[ 
https://issues.apache.org/jira/browse/SOLR-6275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ramkumar Aiyengar updated SOLR-6275:
------------------------------------
    Description: Currently, {{QTime}} uses {{currentTimeMillis}} instead of 
{{nano Time}} and hence is not suitable for time measurements. Further, it is 
really started after all the dispatch logic in {{SolrDispatchFilter}} (same 
with the top level timing reported by {{debug=timing}}) which may or may not be 
expensive, and hence may not fully represent the time taken by the search. This 
is to remedy both cases.  (was: Currently, {{QTime}} uses {{currentTimeMillis}} 
instead of {{nanoTime}} and hence is not suitable for time measurements. 
Further, it is really started after all the dispatch logic in 
{{SolrDispatchFilter}} (same with the top level timing reported by 
{{debug=timing}}) which may or may not be expensive, and hence may not fully 
represent the time taken by the search. This is to remedy both cases.)

> Improve accuracy of QTime reporting
> -----------------------------------
>
>                 Key: SOLR-6275
>                 URL: https://issues.apache.org/jira/browse/SOLR-6275
>             Project: Solr
>          Issue Type: Improvement
>          Components: search
>            Reporter: Ramkumar Aiyengar
>            Assignee: Ramkumar Aiyengar
>            Priority: Minor
>         Attachments: SOLR-6275.patch
>
>
> Currently, {{QTime}} uses {{currentTimeMillis}} instead of {{nano Time}} and 
> hence is not suitable for time measurements. Further, it is really started 
> after all the dispatch logic in {{SolrDispatchFilter}} (same with the top 
> level timing reported by {{debug=timing}}) which may or may not be expensive, 
> and hence may not fully represent the time taken by the search. This is to 
> remedy both cases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to