Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=qHxmAFGu3EKCTwqwO63XatYFng2+rUmsjjdV1pkZEwJDR/XnixLwjcFpskdaTp6EXkSMho3c3NCb8o50PxHP3GwLeSWlfPaOuzxKhSDRfu4wLLM3VYKrqJ6WbGz3yi0zdnu1qyCvwyUfUvuUvSLTNG2pgTJsWxW3xQY0d2k/DZo=
  ;
Message-ID: <20051211073442.5098.qmail@web50301.mail.yahoo.com>
Date: Sat, 10 Dec 2005 23:34:42 -0800 (PST)
From: Otis Gospodnetic <otis_gospodnetic@yahoo.com>
Subject: Re: Can I warm-up my search for it's performance?
To: java-user@lucene.apache.org
In-Reply-To: <48b708490512102330m5ffef0f7l22d349e7ae865546@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Any term will do, although I'd personally choose a very common one.

Otis

--- Cheolgoo Kang <appler@gmail.com> wrote:

> Thanks Otis,
> 
> I'm doing exactly what you've said, except the sorting. I'll try it
> out immediately.
> 
> Anyway, will the warming up search with ANY term do the same job? Or
> should I have to search with the worst term that has the longest
> hits?
> 
> On 12/11/05, Otis Gospodnetic <otis_gospodnetic@yahoo.com> wrote:
> > Yes you can.  Just open an IndexReader/Searcher, say in a separate
> > thread, run a search on it, and then swap your previous
> > IndexReader/Searcher with the warm one.  If you use sorting, make
> your
> > "background query" with the sort option, so the FieldCaches get
> > populated and warmed up.
> >
> > Otis
> >
> > --- Cheolgoo Kang <appler@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > I'm running an index on FSDirectory with 0.4M documents with each
> of
> > > 7 fields.
> > >
> > > When I open an IndexReader and an IndexSearcher, the average
> search
> > > time with hits of 0.2M items (yeah, very common word) takes about
> > > 150~250 msec and it's pretty good. But the first time just after
> > > opening IndexReader or IndexSearcher, search with the same
> keyword
> > > takes about 3~4 secs (10 times more than the average) and this
> makes
> > > our search system looks slow.
> > >
> > > I think it could be the caching issue with OS and file system.
> > >
> > > Any way, can I warm our IndexSearcher or IndexReader up to reduce
> > > this problem?
> > >
> > > --
> > > Cheolgoo
> > >
> > >
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> > > For additional commands, e-mail: java-user-help@lucene.apache.org
> > >
> > >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> > For additional commands, e-mail: java-user-help@lucene.apache.org
> >
> >
> 
> 
> --
> Cheolgoo
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org
> 
> 


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