Has there been any progress on this or tools people might use to capture the
average or 90% time for the last hour?
That would allow us to better match up slowness with other metrics like
CPU/IO/Memory to find bottlenecks in the system.
Thanks,
Ian.
On Wed, Mar 31, 2010 at 9:13 PM, Chris Hostett
: Say I have 3 Cores names core0, core1, and core2, where only core1 and core2
: have documents and caches. If all my searches hit core0, and core0 shards
: out to core1 and core2, then the stats from core0 would be accurate for
: errors, timeouts, totalTime, avgTimePerRequest, avgRequestsPerSeco
: reloading the core just to reset the stats definitely seems like throwing
: out the baby with the bathwater.
Agreed about throwing out the baby with the bath water - if stats need to be
reset, though, then that's the only way today. A reset stats button would
be a nice way to prevent having to
: You can reload the core on which you want to reset the stats - this lets you
: keep the engine up and running without requiring you restart Solr. If you
reloading the core just to reset the stats definitely seems like throwing
out the baby with the bathwater.
: have an separate core for aggr
You can reload the core on which you want to reset the stats - this lets you
keep the engine up and running without requiring you restart Solr. If you
have an separate core for aggregating (i.e. a core that contains no data and
has no caches) then the overhead for reloading that core is negligable
: Is there a way to reset the stats counters? For example in the Query handler
: avgTimePerRequest is not much use after a while as it is an avg since the
: server started.
not at the moment ... but it would probably be fairly straight forward to
add as a new option if you want to file a Jira is
