On 5/13/07, Nadav Har'El <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
