Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of jason.rutherglen@gmail.com
 designates 209.85.221.181 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=j0FQ45YU2bdMtdSpCF/ch1bVg8gU02uq/VBHzUr+RufOwZg2kxYMR7Al0DGO/gFW4h
         ux8BbC0fP+9Ev+JTZyZAXwSVNp29GluoWosNxZSbBBI0A7R8YBseNL2lu89Bn1ur6fY5
         opsFWKyda8EDAp+7IafG2rdSI0XE9l9bppMRI=
MIME-Version: 1.0
In-Reply-To: <8837fb770909212227w7668a2acj8217cb4b0b1cee8f@mail.gmail.com>
References: <8837fb770909212156s13645f84tbee15ee3bd2d5aef@mail.gmail.com>
	 <c68e39170909212205q66b0bb50n8099c7b1237c98d0@mail.gmail.com>
	 <8837fb770909212227w7668a2acj8217cb4b0b1cee8f@mail.gmail.com>
Date: Tue, 22 Sep 2009 08:36:25 -0700
Message-ID: <85d3c3b60909220836o2d1ac620jab32457f61e260e0@mail.gmail.com>
Subject: Re: 2.9 NRT w.r.t. sorting and field cache
From: Jason Rutherglen <jason.rutherglen@gmail.com>
To: java-dev@lucene.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

> When heaving indexing introduces or modifies segments, would
it cause reloading of FieldCache at query time and thus would
impact search performance?

How is this different than previous versions of Lucene? In 2.9
the field caches are only loaded for new segments incrementally,
instead of over the Multi*Reader. It sounds like you're confused
about the key used for the field cache which is now the
freqStream (see IR.getFieldCacheKey) rather than IR so that a
different field cache isn't loaded each time a new instance of
IR is instantiated for an already loaded segment.

Feel free to contribute to the wiki about your experiences, I
think others will have similar questions.

On Mon, Sep 21, 2009 at 10:27 PM, John Wang <john.wang@gmail.com> wrote:
> Hi Yonik:
>
> =A0=A0=A0=A0 Actually that is what I am looking for. Can you please point=
 me to
> where/how sorting is done per-segment?
>
> =A0=A0=A0=A0 When heaving indexing introduces or modifies segments, would=
 it cause
> reloading of FieldCache at query time and thus would impact search
> performance?
>
> thanks
>
> -John
>
> On Tue, Sep 22, 2009 at 1:05 PM, Yonik Seeley <yonik@lucidimagination.com=
>
> wrote:
>>
>> On Tue, Sep 22, 2009 at 12:56 AM, John Wang <john.wang@gmail.com> wrote:
>> > Looking at the code, seems there is a disconnect between how/when fiel=
d
>> > cache is loaded when IndexWriter.getReader() is called.
>>
>> I'm not sure what you mean by "disconnect"
>>
>> > Is FieldCache updated?
>>
>> FieldCache entries are populated on demand, as they always have been.
>>
>> > Otherwise, are we reloading FieldCache for each
>> > reader instance?
>>
>> Searching/sorting is now per-segment, and so is the use of the
>> FieldCache. =A0Segments that don't change shouldn't have to reload their
>> FieldCache entries.
>>
>> -Yonik
>> http://www.lucidimagination.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
>> For additional commands, e-mail: java-dev-help@lucene.apache.org
>>
>
>

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