No, Lucene itself shouldn't be doing this, the recommendation is for multiple threads to share a single searcher. I'd first look upstream, are your requests being processed serially? I.e. is there a single thread that's handling requests?
Best Erick On Thu, Mar 10, 2011 at 4:25 PM, RobM <rmcclana...@databanq.com> wrote: > I currently have two types of searches on my website that are using the same > index and same instance of index searcher. One of the searches usually only > takes 50 - 100 milliseconds but the second usually takes 2 seconds. It seems > as though when someone does the second search and another user does the > first search immediately after the first search will wait for the second to > complete. Is that how Lucene works or am I just looking at my test wrong. If > so how should i solve this issue? Two indexes or two index searchers? > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/IndexSearcher-Single-Instance-Bottleneck-tp2662376p2662376.html > Sent from the Lucene - Java Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
