[
https://issues.apache.org/jira/browse/SOLR-1972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13540211#comment-13540211
]
Shawn Heisey commented on SOLR-1972:
------------------------------------
Lance, I see two other problems with OnlineSummarizer.
1) There are only 100 samples. That's apparently enough for 0/25/50/75/100
quartiles, but it seems very low for 95/99. I was even worried about the 1024
samples in the metrics library, but apparently it actually works very well.
2) Solr already includes mahout-math 0.3 as a dependency of carrot2.
OnlineSummarizer was introduced in 0.4, and there are some serious bugs in it
as late as 0.6. Upgrading mahout-math to 0.7 causes clustering (carrot2) tests
to fail because it can't find a mahout class. Even the newest version of
carrot2 depends specifically on mahout-math 0.3.
I have a checkout where I am re-applying the metrics patch and have made
RequestHandlerBase implement Closeable, but I have zero knowledge about where
the close() method would actually have to be called. I have been attempting to
figure it out, but Solr is a very large and complex codebase, so I will need
some help. I'm almost always idling in #lucene and #solr as 'elyograg' if
someone wants to give me some live pointers. I can do the actual work, but I
need some help figuring out where handlers are created and destroyed.
> 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.2, 5.0
>
> Attachments: elyograg-1972-3.2.patch, elyograg-1972-3.2.patch,
> elyograg-1972-trunk.patch, elyograg-1972-trunk.patch, leak-closeable.patch,
> leak.patch, revert-SOLR-1972.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_metrics.patch, SOLR-1972_metrics.patch, SOLR-1972_metrics.patch,
> SOLR-1972_metrics.patch, solr1972-metricsregistry-branch4x-failure.log,
> SOLR-1972.patch, SOLR-1972.patch, SOLR-1972.patch, SOLR-1972.patch,
> SOLR-1972-url_pattern.patch, stacktraces.tar.gz
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
