lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shawn Heisey (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-1972) Need additional query stats in admin interface - median, 95th and 99th percentile
Date Thu, 12 Apr 2012 18:49:18 GMT

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

Shawn Heisey commented on SOLR-1972:
------------------------------------

Let's have everyone pretend for a minute that I have a slightly better grasp of Solr/Lucene
internals than I actually do.  Perhaps I will one day be able to take what you say and figure
out what it means.  I am very interested in having these stats available without patching
Solr on my own.

What would be the right way to go about re-implementing this as a module (along with some
unit tests) so the code could be committed?

                
> 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-branch3x-url_pattern.patch, SOLR-1972-url_pattern.patch,
SOLR-1972.patch, SOLR-1972.patch, SOLR-1972.patch, SOLR-1972.patch, elyograg-1972-3.2.patch,
elyograg-1972-3.2.patch, elyograg-1972-trunk.patch, elyograg-1972-trunk.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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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


Mime
View raw message