Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Sat, 11 Jun 2011 12:58:59 +0000 (UTC)
From: "Adrien Grand (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <1261608985.13730.1307797139003.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (SOLR-1972) Need additional query stats in admin
 interface - median, 95th and 99th percentile
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Adrien Grand updated SOLR-1972:
-------------------------------

    Attachment: SOLR-1972.patch

This patches adds rolling statistics (same as non-rolling statistics, plus median and 75/90/99 percentiles) to request handlers.

Rolling statistics are off by default because they require synchronization, but the critical section is very small so no overhead should be noticeable.

> Need additional query stats in admin interface - median, 95th and 99th percentile
> ---------------------------------------------------------------------------------
>
>                 Key: SOLR-1972
>                 URL: https://issues.apache.org/jira/browse/SOLR-1972
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 1.4
>            Reporter: Shawn Heisey
>            Priority: Minor
>         Attachments: SOLR-1972.patch
>
>
> I would like to see more detailed query statistics from the admin GUI.  This is what you can get now:
> requests : 809
> errors : 0
> timeouts : 0
> totalTime : 70053
> avgTimePerRequest : 86.59209
> avgRequestsPerSecond : 0.8148785 
> I'd like to see more data on the time per request - median, 95th percentile, 99th percentile, and any other statistical function that makes sense to include.  In my environment, the first bunch of queries after startup tend to take several seconds each.  I find that the average value tends to be useless until it has several thousand queries under its belt and the caches are thoroughly warmed.  The statistical functions I have mentioned would quickly eliminate the influence of those initial slow queries.
> The system will have to store individual data about each query.  I don't know if this is something Solr does already.  It would be nice to have a configurable count of how many of the most recent data points are kept, to control the amount of memory the feature uses.  The default value could be something like 1024 or 4096.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

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