Re: Huge performance drop in distributed search w/ shards on the same server/container

2011-06-14 Thread Johannes Goll
I increased the maximum POST size and headerBufferSize to 10MB ; lowThreads to 50, maxThreads to 10 and lowResourceMaxIdleTime=15000. We tried tomcat 6 using the following Connnector settings : I am getting the same exception as for jetty SEVERE: org.apache.solr.common.SolrException: org.ap

Re: Huge performance drop in distributed search w/ shards on the same server/container

2011-06-13 Thread Yonik Seeley
On Sun, Jun 12, 2011 at 9:10 PM, Johannes Goll wrote: > However, sporadically, Jetty 6.1.2X (shipped with  Solr 3.1.) > sporadically throws Socket connect exceptions when executing distributed > searches. Are you using the exact jetty.xml that shipped with the solr example server, or did you make

Re: Huge performance drop in distributed search w/ shards on the same server/container

2011-06-12 Thread Johannes Goll
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

Re: Huge performance drop in distributed search w/ shards on the same server/container

2011-05-26 Thread pravesh
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 di

Re: Huge performance drop in distributed search w/ shards on the same server/container

2011-05-15 Thread Frederik Kraus
Any ideas? On Freitag, 13. Mai 2011 at 13:19, Frederik Kraus wrote: > One Tomcat with multicore. I have a list of about 2mio "real" queries that > I'm firing at the cluster with jmeter. Reason for splitting up the index in > rather small parts is that the maximum response time of 1 sec cannot be

Re: Huge performance drop in distributed search w/ shards on the same server/container

2011-05-13 Thread Frederik Kraus
One Tomcat with multicore. I have a list of about 2mio "real" queries that I'm firing at the cluster with jmeter. Reason for splitting up the index in rather small parts is that the maximum response time of 1 sec cannot be exceeded for any of those queries. On Freitag, 13. Mai 2011 at 12:57,

Re: Huge performance drop in distributed search w/ shards on the same server/container

2011-05-13 Thread Grant Ingersoll
Is that 10 different Tomcat instances or are you using multicore? How are you testing? On May 13, 2011, at 6:08 AM, Frederik Kraus wrote: > Hi, > > I'm having some serious problems scaling the following setup: > > 48 CPU / Tomcat / ... > > localhost/shard1 > ... > localhost/shard10 > > Whe