On Wed, Feb 3, 2010 at 1:33 PM, tsuraan wrote:
> > The FieldCache loads per segment, and the NRT reader is reloading only
> > new segments from disk, so yes, it's "smarter" about this caching in this
> > case.
>
> Ok, so the cache is tied to the index, and not to any particular
> reader. The act
> The FieldCache loads per segment, and the NRT reader is reloading only
> new segments from disk, so yes, it's "smarter" about this caching in this
> case.
Ok, so the cache is tied to the index, and not to any particular
reader. The actual FieldCacheImpl keeps a mapping from Reader to its
terms,
The FieldCache loads per segment, and the NRT reader is reloading only
new segments from disk, so yes, it's "smarter" about this caching in this
case.
-jake
On Wed, Feb 3, 2010 at 1:07 PM, tsuraan wrote:
> Is the cache used by sorting on strings separated by reader, or is it
> a global thing?
Is the cache used by sorting on strings separated by reader, or is it
a global thing? I'm trying to use the near-realtime search, and I
have a few indices with a million docs apiece. If I'm opening a new
reader every minute, am I going to have every term in every sort field
read into RAM for each
