Sorry for the awful word wrapping in original email. The main thing is to warm those caches up (sure, by autowarming for example) before exposing the searcher. In other words, don't hit the completely cold searcher with a bunch of requests at once.
Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch ----- Original Message ---- > From: Ziqi Zhang <[EMAIL PROTECTED]> > To: solr-user@lucene.apache.org > Sent: Wednesday, February 6, 2008 7:56:46 PM > Subject: Re: how to improve concurrent request performance and stress testing > > Thanks! > > > > Also > make > sure > that > common > filters, > sort > fields, > and > facets > have > been > > > warmed. > > I > assume > these > are > achieved > by > setting > large > cache > size > and > large > autowarmcount > number > in > solr > configuration? > specifically > > filterCache > queryResultCache > documentCache > > Thanks! > > > -------------------------------------------------- > From: > "Yonik > Seeley" > > Sent: > Wednesday, > February > 06, > 2008 > 7:50 > AM > To: > > Subject: > Re: > how > to > improve > concurrent > request > performance > and > stress > testing > > > > On > Feb > 6, > 2008 > 6:37 > PM, > Ziqi > Zhang > > wrote: > >> > I > still > do > not > understand > why > sending > 100 > request > (of > same > query) > from > >> > 100 > >> > threads > throws > solr > server > to > silence > - > is > it > because > of > the > >> > computational > >> > cost > to > deal > with > same > query > in > 100 > separate > threads? > > > > > Yes... > sending > a > large > number > of > requests > at > once > can > cause > one > to > > > start > hitting > synchronization > bottlenecks. > > > > > > -Yonik > > >
