again. If you where doing
relevancy sorting you would not experience such a big delay.
- Mark
Bryan Dotzour wrote:
> Otis thanks for your suggestion, it seems to be working pretty well!
> I'm just curious if you (or anyone else) could describe what is
actually
> happening during th
mon query.
For warming up new indices, one can also use the `dd' trick under UNIX.
Otis
- Original Message
From: Bryan Dotzour <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Wednesday, December 20, 2006 5:23:40 PM
Subject: RE: First search is slow after updating in
, and then switch IndexReader/Searchers, closing the old
one.
Otis
- Original Message ----
From: Bryan Dotzour <[EMAIL PROTECTED]>
To: java-user@lucene.apache.org
Sent: Wednesday, December 20, 2006 3:59:19 PM
Subject: First search is slow after updating index .. subsequent
searche
Cache population. The cure for that is to open a new
IndexReader/Searcher before you close the old one, warm it up with a
query + sort, and then switch IndexReader/Searchers, closing the old
one.
Otis
- Original Message
From: Bryan Dotzour <[EMAIL PROTECTED]>
To: java-user@lucene.apac
I'm investigating some performance issues with the way we're using
Lucene in our web app and am interested if anyone could shed some light
on what might be going on. Hopefully I can provide enough information,
please let me know if there's more I can give.
We're using Lucene 2.0.0 and I'm curr
