lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley" <yo...@apache.org>
Subject Re: IndexReader.isCurrent in presence of many files
Date Sun, 13 May 2007 13:56:11 GMT
On 5/13/07, Nadav Har'El <nyh@math.technion.ac.il> wrote:
> > >However, isCurrent() may be called before every query.
> >
> > That's never going to be a high performance architecture.
>
> Why is that so?
> Potentially, isCurrent() could do a couple of disk accesses (and usually
> cached by the operating system), which is much faster than running the
> actual query, which needs to read a lot more from disk (of course, that
> is often cached as well) and do a lot more processing.

I was thinking about the scenario of a moderate to high update rate that would
cause the IndexReader to be re-opened multiple times per second (presumably
that's why someone would want to call isCurrent()).

-Yonik

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


Mime
View raw message