lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anson Lau" <>
Subject RE: best ways of using IndexSearcher
Date Tue, 29 Jun 2004 07:55:39 GMT

Thanks for the advice.  When you say "This stuff is not really CPU
intensive" are you refering to the search itself or something else?  In my
experience the search tends to be ultimately bounded by CPU.


-----Original Message-----
From: Otis Gospodnetic [] 
Sent: Tuesday, June 29, 2004 2:51 PM
To: Lucene Users List
Subject: Re: best ways of using IndexSearcher


Use a single instance of IndexSearcher and, if you want to always 'see'
even the latest index changes (deletes and adds since you opened the
IndexSearcher) make sure to re-create the IndexSearcher when you detect
that the index version has changed (see

When you get the new IndexSearcher, leave the old instance alone - let
the GC take care of it, and don't call close() on it, in case something
in your application is still using that instance.

This stuff is not really CPU intensive.  Disk I/O tends to be the
bottleneck.  If you are working with multiple indices, spread them over
multiple disks (not just partitions, real disks), if you can.


--- Anson Lau <> wrote:
> Hi Guys,
> What's the recommended way of using IndexSearcher? Should
> IndexSearcher be a
> singleton or pooled?  Would pooling provide a more scalable solution
> by
> allowing you to decide how many IndexSearcher to use based on say how
> many
> CPU u have on ur server?
> Thanks,
> Anson

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message