As you add nodes, the average response time of the slowest node will likely increase. For example, consider an extreme case where you have something like 1 million nodes - you're practically guaranteed that one of them is going to be doing something like a stop-the-world garbage collection. So even if 999,999 return in 10ms, there's going to be that one slowpoke that takes 1000ms, and it doesn't matter how fast the other 999,999 are.
-Michael -----Original Message----- From: Mark Miller [mailto:markrmil...@gmail.com] Sent: Wednesday, December 05, 2012 11:00 PM To: solr-user@lucene.apache.org Subject: Re: SolrCloud - Query performance degrades with multiple servers This is just the std scatter gather distrib search stuff solr has been using since around 1.4. There is some overhead to that, but generally not much. I've measured it at around 30-50ms for a 100 machines, each with 10 million docs a few years ago. So...that doesn't help you much...but FYI... - Mark On Dec 5, 2012, at 5:35 PM, sausarkar <sausar...@ebay.com> wrote: > We are using SolrCloud and trying to configure it for testing purposes, we > are seeing that the average query time is increasing if we have more than > one node in the SolrCloud cluster. We have a single shard 12 gigs > index.Example:1 node, average query time *~28 msec* , load 140 > queries/second3 nodes, average query time *~110 msec*, load 420 > queries/second distributed equally on three servers so essentially 140 qps > on each node.Is there any inter node communication going on for queries, is > there any setting on the Solrcloud for query tuning for a cloud config with > multiple nodes.Please help. > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/SolrCloud-Query-performance-degrades-with-multiple-servers-tp4024660.html > Sent from the Solr - User mailing list archive at Nabble.com.
