[
https://issues.apache.org/jira/browse/SOLR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13482470#comment-13482470
]
Shawn Heisey edited comment on SOLR-1972 at 10/23/12 5:13 PM:
--------------------------------------------------------------
This is lightyears beyond what I could have hoped for when I first opened this
issue. I do have one more picky note: the extreme floating point precision of
the output. Here's what I am getting:
handlerStart: 1351011529717
requests: 14
errors: 0
timeouts: 0
totalTime: 53483.059463
avgTimePerRequest: 3820.2185330714287
avgRequestsPerSecond: 0.1592740558481214
5minRateReqsPerSecond: 0.6393213424767414
15minRateReqsPerSecond: 0.7422605686168207
medianRequestTime: 2537.401157
75thPcRequestTime: 7728.151086
95thPcRequestTime: 8963.867643
99thPcRequestTime: 8963.867643
999thPcRequestTime: 8963.867643
Here's what I would like to see instead ... lower precision, and rounded up
when the first eliminated digit is 5 or higher.
handlerStart: 1351011529717
requests: 14
errors: 0
timeouts: 0
totalTime: 53483
avgTimePerRequest: 3820.22
avgRequestsPerSecond: 0.16
5minRateReqsPerSecond: 0.64
15minRateReqsPerSecond: 0.74
medianRequestTime: 2537.40
75thPcRequestTime: 7728.15
95thPcRequestTime: 8963.87
99thPcRequestTime: 8963.87
999thPcRequestTime: 8963.87
was (Author: elyograg):
This is lightyears beyond what I could have hoped for when I first opened
this issue. I do have one more picky note: the extreme floating point
precision of the output. Here's what I am getting:
handlerStart: 1351011529717
requests: 14
errors: 0
timeouts: 0
totalTime: 53483.059463
avgTimePerRequest: 3820.2185330714287
avgRequestsPerSecond: 0.1592740558481214
5minRateReqsPerSecond: 0.6393213424767414
15minRateReqsPerSecond: 0.7422605686168207
medianRequestTime: 2537.401157
75thPcRequestTime: 7728.151086
95thPcRequestTime: 8963.867643
99thPcRequestTime: 8963.867643
999thPcRequestTime: 8963.867643
Here's what I would like to see instead ... lower precision, and rounded up
when the first eliminated digit is 5 or higher.
handlerStart: 1351011529717
requests: 14
errors: 0
timeouts: 0
totalTime: 53483
avgTimePerRequest: 3820
avgRequestsPerSecond: 0.16
5minRateReqsPerSecond: 0.64
15minRateReqsPerSecond: 0.74
medianRequestTime: 2537.40
75thPcRequestTime: 7728.15
95thPcRequestTime: 8963.87
99thPcRequestTime: 8963.87
999thPcRequestTime: 8963.87
> 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: 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.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-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
