Thank you, you are right ! It seems to be a congestion from our test tool.
Regards,
2016-01-19 18:46 GMT+01:00 Toke Eskildsen :
> Damien Picard wrote:
> > Currently we have 4 Solr nodes, with 12Gb memory (heap) ; the collections
> > are replicated (4 shards, 1 replica).
> > This query mostly re
Damien Picard wrote:
> Currently we have 4 Solr nodes, with 12Gb memory (heap) ; the collections
> are replicated (4 shards, 1 replica).
> This query mostly returns a QTime=4 and it takes around 20ms on the client
> side to get the result.
> We have to handle around 200 simultaneous connections.
Thank you for your advices.
Currently we have 4 Solr nodes, with 12Gb memory (heap) ; the collections
are replicated (4 shards, 1 replica).
This query mostly returns a QTime=4 and it takes around 20ms on the client
side to get the result.
We have to handle around 200 simultaneous connections.
Cu
On 1/19/2016 3:43 AM, Damien Picard wrote:
> I'm currently testing Solr query execution performance (over http and
> SolrJ), and, using HTTP with JMeter, I see that the response time increases
> with the number of concurrent request (100 simultaneous request in my case).
>
> To understand where Sol
Hi,
I'm currently testing Solr query execution performance (over http and
SolrJ), and, using HTTP with JMeter, I see that the response time increases
with the number of concurrent request (100 simultaneous request in my case).
To understand where Solr takes more time, I use the debug=timing param
