Unfortunately, in Lucene 2.4, any query that needs to enumerate Terms
(Prefix, Wildcard, Range, etc.) has poor performance on Multi*Readers.
 I think the only workaround is to merge your indexes down to a single
index.

But, Lucene trunk (not yet released) has fixed this, so that searching
through your MultiReader should give you the same performance as
searching on a single consolidated index -- if you test this (which
would be awesome!) please report back and let us know how it went.

Mike

On Fri, Apr 10, 2009 at 10:38 AM, Raf <r.ventag...@gmail.com> wrote:
> Hi,
> we are experiencing some problems using RangeFilters and we think there are
> some performance issues caused by MultiReader.
>
> We have more or less 3M documents in 24 indexes and we read all of them
> using a MultiReader.
> If we do a search using only terms, there are no problems, but it if we add
> to the same search terms a RangeFilter that extracts a large subset of the
> documents (e.g. 500K), it takes a lot of time to execute (about 15s).
>
> In order to identify the problem, we have tried to consolidate the index: so
> now we have the same 3M docs in a single 10GB index.
> If we repeat the same search using this index, it takes only a small
> fraction of the previous time (about 2s).
>
> Is there something we can do to improve search performance using
> RangeFilters with MultiReader or the only solution is to have only a single
> big index?
>
> Thanks,
> Raf
>

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

Reply via email to