lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Miller <markrmil...@gmail.com>
Subject Re: CachingWrapperFilter: why cache per IndexReader?
Date Tue, 01 Jan 2008 21:24:53 GMT
I believe that, in general, you'll find that ParallelMultiSearcher is 
much slower than just using a MultiSearcher. ParralelMultiSeacher is of 
use when you can put the different indexes on separate hard drives or 
even better, separate systems (using RMI or something).

- Mark

Timo Nentwig wrote:
> On Tuesday 01 January 2008 21:06:06 Mark Miller wrote:
>   
>> The main reason to use a single IndexReader is because its very time
>> consuming to open an IndexReader. If your index is pretty static, maybe
>>     
>
> Yes, it takes quite some time to build it and it's not changed but rebuilt 
> from scratch.
>
>   
>> Perhaps, in some esoteric case, multiple readers is the right idea
>>     
>
> I recently talked to a guy how stated that they'd solved their performance 
> issues by breaking up the index into multiple sub-indices and searching them 
> in parallel (probably using ParallelMultiSearcher)...hmm, well, I've had (and 
> still have) my doubts but on the other hand what's the benefit of 
> ParallelMultiSearcher if it doesn't scale better than searching a monolithic 
> index?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
>
>
>   

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


Mime
View raw message