Hi Aswath,
It is not common to test only QPS unless it is static index most of the
time. Usually you have to test and tune worst case scenario - max
expected indexing rate + queries. You can get more QPS by reducing query
latency or by increasing number of replicas. You manage latency by
tunin
t;
> >
> > -Original message-
> >> From:Aswath Srinivasan (TMS)
> >> Sent: Tuesday 17th November 2015 23:46
> >> To: solr-user@lucene.apache.org
> >> Subject: Performance testing on SOLR cloud
> >>
> >> Hi fellow develope
ry times and load tend to regress to the mean and b) because
> HotSpot needs to 'warm up' so short tests make less sense.
>
> M.
>
>
>
> -Original message-
>> From:Aswath Srinivasan (TMS)
>> Sent: Tuesday 17th November 2015 23:46
>> To: solr-us
and b) because
HotSpot needs to 'warm up' so short tests make less sense.
M.
-Original message-
> From:Aswath Srinivasan (TMS)
> Sent: Tuesday 17th November 2015 23:46
> To: solr-user@lucene.apache.org
> Subject: Performance testing on SOLR cloud
>
> H
Hi fellow developers,
Please share your experience, on how you did performance testing on SOLR? What
I'm trying to do is have SOLR cloud on 3 Linux servers with 16 GB RAM and index
a total of 2.2 million. Yet to decide how many shards and replicas to have (Any
hint on this is welcome too, basic
