Distributed search requires more work (more than one pass.) If you weren't CPU bound to begin with, it's definitely going to make things worse by splitting up the index on the same box.
-Yonik On Thu, Jan 8, 2009 at 3:53 PM, smock <harish.agar...@gmail.com> wrote: > > Hi All, > > I'm very new to Solr, and also fairly new Java and servlet containers, etc. > I'm trying to set up Solr on a single machine with a distributed index. My > current implementation uses Tomcat as a servlet container with multiple > instances of Solr being served. Each instance of Solr is a shard of my > index. I have two shards as I'm running this setup on a dual processor > machine. > > I'm benchmarking this setup and would expect that, given the two processors, > search times for one shard would be roughly the same as search times across > both. However, I'm finding that search times are about double when > searching across both shards, which seems to indicate that both processors > are not being used efficiently. > > Does anyone have any advice on what I might be doing wrong? Spreading > things across different machines is not an option. Both indexes are being > run off of the same disk, but this was also the case with my prior > distributed search solution (using sphinx) in which I did see the expected > performance boost. > > Thanks, > -Harish > -- > View this message in context: > http://www.nabble.com/Solr-on-a-multiprocessor-machine-tp21360747p21360747.html > Sent from the Solr - User mailing list archive at Nabble.com. > >
