hi ,
am also confused abt the same when doing the maths results are different
rajat
--
View this message in context:
http://lucene.472066.n3.nabble.com/Meaning-of-avgTimePerRequest-avgRequestsPerSecond-in-SOLR-stats-page-tp1922692p3984848.html
Sent from the Solr - User mailing list archive at N
Thanks Erick.
--
View this message in context:
http://lucene.472066.n3.nabble.com/Meaning-of-avgTimePerRequest-avgRequestsPerSecond-in-SOLR-stats-page-tp1922692p1932275.html
Sent from the Solr - User mailing list archive at Nabble.com.
avgTimePerRequest is the important one for your users. They don't care if
you're processing
a million QPS, they care how long *their* query took. But you also have to
pay attention
to longest response times
Best
Erick
On Thu, Nov 18, 2010 at 12:54 PM, Shanmugavel SRD
wrote:
>
> Erick,
> Th
Erick,
Thanks a lot for explaining about these two fields.
Could you please let us know which one we have to look for if we have to
monitor the performance? avgTimePerRequest OR avgRequestsPerSecond.
Thanks,
SRD
--
View this message in context:
http://lucene.472066.n3.nabble.com/Meaning-o
No, that's not true. As long as you're not limited by some resource,
avgRequestsPerSecond can grow without impacting avgTimePerRequest
much.
avgTimePerRequest is the elapsed time from the beginning of Solr handling
the request to the end, measured in clock time. Say it takes 100 ms. Of
that 100 ms
We have recently upgraded some of our solr instances to 1.4.1 from 1.3.
Interestingly both these parameter values got increased after our upgrade.
When avgRequestsPerSecond increases, avgTimePerRequest should be increased.
But it is not in our case..
Any thoughts ?
--
View this message in conte
average time per request is
the total time spent servicing X requests divided by X (in milliseconds I
believe).
If no searches are being processed, this number doesn't change.
It's a measure of how long it takes, on average, to service a single
request.
avrRequests per second is the total time sin
