lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erick Erickson <>
Subject Re: Searching slow *after* an optimize ( 2.3.2)
Date Thu, 22 Oct 2009 12:42:00 GMT
Check this out with the .net port folks, but in the Java world, whenyou open
an IndexReader (which I presume you do after optimizing),
the first few queries fill various caches etc. and do run slowly. One
solution is to fire a few warmup queries at the newly opened reader
before letting your main application start using that same reader.

I'm surprised that it takes 15 minutes for things to settle down.
When you post on the .net forum, you should include the amount
of memory you're allocating to the process as well as other
details, like what *else* is running on your searcher.


On Thu, Oct 22, 2009 at 7:17 AM, ShibbyUK <> wrote:

> Hi,
> We're having some odd performance problems. Recently, searching our index
> is
> becoming slow *after* performing an optimize. This is counter intuitive as
> usually the optimize has the opposite effect!
> We're using 2.3.2 and have an index of 250,000 documents and
> about 500 queries per minute at peak times.
> Performance is good (even after much indexing) until the optimize runs.
> Then, queries are slow (2-5 seconds) for about 15 minutes until eventually
> settling down a bit. But in this time, many query threads time out (as we
> queue when we have to). We are not using any explicit caching methods.
> Any help/suggestions on what to do would be much appreciated! I'm about to
> rebuild the index from scratch to see if this temporarily resolves the
> problem...
> Thanks
> --
> View this message in context:
> Sent from the Lucene - Java Users mailing list archive at
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message