Hi Fred, we are having similar issues of scaling Solr 3.1 distributed searches on a single box with 18 cores. We use the StatsComponent which seems to be mainly CPU bound. Using distributed searches resulted in a 9 fold decrease in response time. However, sporadically, Jetty 6.1.2X (shipped with Solr 3.1.) sporadically throws Socket connect exceptions when executing distributed searches. Our next step is to switch from from jetty to tomcat. Did you find a solution for improving the CPU utilization and requests per second for your system?
Johannes 2011/5/26 pravesh <suyalprav...@yahoo.com> > Do you really require multi-shards? Single core/shard will do for even > millions of documents and the search will be faster than searching on > multi-shards. > > Consider multi-shard when you cannot scale-up on a single > shard/machine(e.g, > CPU,RAM etc. becomes major block). > > Also read through the SOLR distributed search wiki to check on all tuning > up > required at application server(Tomcat) end, like maxHTTP request settings. > For a single request in a multi-shard setup internal HTTP requests are made > through all queried shards, so, make sure you set this parameter higher. > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Huge-performance-drop-in-distributed-search-w-shards-on-the-same-server-container-tp2938421p2988464.html > Sent from the Solr - User mailing list archive at Nabble.com. > -- Johannes Goll 211 Curry Ford Lane Gaithersburg, Maryland 20878
