Yes, that answers the first part of my question, thanks. So saying N (equally heavy) queries agains N CPUs would run simultaneously, right?
Previous posting suggest high qps rate can be solved perfomance-wise by having high replicationFactor. But what's the benefit (performance wise) compared to having a single replica served by many CPU's? On Tue, Jun 18, 2013 at 12:14 AM, Otis Gospodnetic < otis.gospodne...@gmail.com> wrote: > If I understand your question correctly - what happens with Solr and N > parallel queries is not much different from what happens with N > processes running in the OS - they all get a slice of the CPU time to > do their work. Not sure if that answers your question...? > > Otis > -- > Solr & ElasticSearch Support > http://sematext.com/ > > > > > > On Mon, Jun 17, 2013 at 4:32 PM, Manuel Le Normand > <manuel.lenorm...@gmail.com> wrote: > > Hello all, > > Assuming I have a single shard with a single core, how do run > > multi-threaded queries on Solr 4.x? > > > > Specifically, if one user sends a heavy query (legitimate wildcard query > > for 10 sec), what happens to all other users quering during this period? > > > > If the repsonse is that simultaneous queries (say 2) run multi-threaded, > a > > single CPU would switch between those two query-threads, and in case of 2 > > CPU's each CPU would run his own thread. But the latter case does not > give > > any advantage to repFactor > 1 perfomance speaking, as it's close to same > > as a single replica running wth >1 CPU's. So I am bit confused about > this, > > > > Thanks, > > > > Manu >
