Re: [CLucene-dev] Performance questions

[Itamar Syn-H. <it...@co...>]

Borek,

That is a good question. My gut tells me it all depends on your scenario 
and configurations, and you'd do best to just benchmark and see.

Reusing an IndexSearcher is definitely necessary, but if you'll be using 
one searcher for multiple users then you'll have to implement some sort 
of locking mechanism, and this may introduce performance hit. Having one 
searcher per user is safer and faster, but will require more RAM. 
Perhaps having a pool of searchers where you "fish" one whenever you 
need to perform a search is the best idea: you then keep the amount of 
searchers to the minimum necessary, but still are not suffering from too 
many locks.

My be a good idea to ask this at java-user@l.a.o, there you may find 
people who had this problem before with Lucene Java.

Itamar.

On 23/7/2010 1:22 PM, Kostka Bořivoj wrote:
> Hi,
>
> I'm looking for some hints on server type application architecture from optimal CLucene search usage point of view.
> Questions like:
>
> Share IndexSearcher objects between users or dedicate one for each user
> What is the optimal number of IndexSearcher objects
> One large index or smaller indexes serched in parallel
>
> etc.
>
> I'm not able to find anything.
> If somebody could provide me any useful links it will be very helpful
>
> Thanks
>
> Borek
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> CLucene-developers mailing list
> CLu...@li...
> https://lists.sourceforge.net/lists/listinfo/clucene-developers
>
>
>