Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Thu, 27 Nov 2014 03:42:12 +0000 (UTC)
From: "Mark Miller (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: <JIRA.12729499.1406222143000.32372.1417059732856@Atlassian.JIRA>
In-Reply-To: <JIRA.12729499.1406222143000@Atlassian.JIRA>
References: <JIRA.12729499.1406222143000@Atlassian.JIRA>
 <JIRA.12729499.1406222143530@arcas>
Subject: [jira] [Commented] (SOLR-6275) Improve accuracy of QTime reporting
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SOLR-6275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14227221#comment-14227221 ] 

Mark Miller commented on SOLR-6275:
-----------------------------------

Sorry - been inactive for a while. Could I ask you to bring this one up to date as well :)

> 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: Mark Miller
>            Priority: Minor
>
> 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.


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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org