You may want to utilise Document routing (_route_) option to have your query serve faster but above you are trying to compare apple with oranges meaning your performance tests numbers have to be based on either your actual numbers like 3-5 million docs per shard or sufficient enough to see advantage of using sharding. 10K is nothing for your performance tests and will not give you anything.
Otherwise as Eric mentioned don't shard and add replica's if there is no need to distribute/divide data into shards. See https://cwiki.apache.org/confluence/display/solr/Shards+and+Indexing+Data+in+SolrCloud https://cwiki.apache.org/confluence/display/solr/Advanced+Distributed+Request+Options Thanks, Susheel On Tue, Jul 19, 2016 at 1:41 AM, kasimjinwala <jinwala.ka...@gmail.com> wrote: > This is just for performance testing we have taken 10K records per shard. > In > live scenario it would be 30L-50L per shard. I want to search document from > all shards, it will slow down and take too long time. > > I know in case of solr Cloud, it will query all shard node and then return > result. Is there any way to search document in all shard with best > performance(qps) > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SolrCloud-Query-performance-degrades-with-multiple-servers-tp4024660p4287763.html > Sent from the Solr - User mailing list archive at Nabble.com. >
