On 9/6/2018 8:50 AM, isabella.ghiurea(a)nrc-cnrc.gc.ca wrote:
This does not justify this since running 1 tread takes 0.1564msec/op
and running 10 threads takes 0.0590ms/op and the last one will require the access.log to
be flush more frequently I think for 10 threads and I do not see the spike in exec
time showed for 1 thread. Maybe something else ?
_______________________________________________
I think, looking at the data you posted, the question you're asking is
"why, when I subject my server to a continuous search operation load, do
some operations have much longer latency than others?".
This isn't a performance issue per se, imho because performance overall
is acceptable. The problem is that rsearch reports a maximum search
response time that is quite high. That maximum could have been measured
on only _one_ operation though.