lucene-dev mailing list archives

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

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

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

I wanted to double-check that the new test would fail with the old constructor, so I installed
your new patch and removed this.toString() from the parameter list on those statements.

The updated RequestHandlerTests didn't fail like I'd hoped.  I suspect that's because the
terms handler and the update handler are different classes, so this.getClass() was apparently
different.  Before the fix, I did have different statistics in the update handler versus the
search handlers.  It was only handlers of the same type that were the same -- my four search
handlers.

I did however get a rather spectacular (and repeatable) failure in MBeansHandlerTest.  That
failure went away when I restored the constructor to the current patch state.  When I make
it into the office, I will do some additional testing to make sure I did everything right.

                
> 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
>          Components: web gui
>    Affects Versions: 1.4
>            Reporter: Shawn Heisey
>            Assignee: Alan Woodward
>            Priority: Minor
>             Fix For: 4.1
>
>         Attachments: elyograg-1972-3.2.patch, elyograg-1972-3.2.patch, elyograg-1972-trunk.patch,
elyograg-1972-trunk.patch, SOLR-1972-branch3x-url_pattern.patch, SOLR-1972-branch4x.patch,
SOLR-1972-branch4x.patch, SOLR-1972_metrics.patch, SOLR-1972_metrics.patch, SOLR-1972_metrics.patch,
SOLR-1972_metrics.patch, SOLR-1972.patch, SOLR-1972.patch, SOLR-1972.patch, SOLR-1972.patch,
SOLR-1972-url_pattern.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
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