Well, it matters because your single-threaded client is firing one request, waiting for the response, then firing another. There's no opportunity for Solr to use more than one thread for queries if there's only a single thread on a single client ever making requests....
Or I misunderstand what you've set up completely. Best Erick On Wed, Feb 20, 2013 at 8:37 AM, Manuel Le Normand < manuel.lenorm...@gmail.com> wrote: > Yes, i made a one threaded script which sends a querry by a post request to > the shard's url, gets back the response and posts the next querry. > How can it matter? > Manuel > > On Wednesday, February 20, 2013, Erick Erickson wrote: > > > Silly question perhaps, but are you feeding queries at Solr with a > single > > thread? Because Solr uses multiple threads to search AFAIK. > > > > Best > > Erick > > > > > > On Wed, Feb 20, 2013 at 4:01 AM, Manuel Le Normand < > > manuel.lenorm...@gmail.com <javascript:;>> wrote: > > > > > More to it, i do see 75 more threads under the process of tomcat6, but > > only > > > a single one is working while querrying > > > > > > On Wednesday, February 20, 2013, Manuel Le Normand wrote: > > > > > > > Hello, > > > > I created a single collection on a linux server with 8m docs. Solr > 4.1 > > > > While making performance tests, i see that my quad core server makes > a > > > > full use of a single core while the 3 others are idle. > > > > Is there a possibility of making a single sharded collection > available > > > for > > > > multi-threaded querry? > > > > P.s: im not indexing while querrying > > > > > > > > > >
