Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (herse.apache.org: local policy)
Date: Thu, 24 May 2007 10:22:05 +0100
From: Simon Wistow <simon@thegestalt.org>
To: Lucene <java-user@lucene.apache.org>
Subject: Searching on a Rapidly changing Index
Message-ID: <20070524092205.GH5135@thegestalt.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i

I've built a Lucene system that gets rapidly updated - documents are 
supposed to be searchable immeidately after they've been indexed.

As such I have a Writer that puts new index, update and delete tasks 
into a queue and then has a thread which consumes them and applies them 
to the index using one instance of an IndexModifier. So far so good.

However every new Search opens up a new IndexSearcher in order to make 
sure that it gets new documents. The docs indicate is a big 
performance penalty. 

Are there any tips or tricks I can use to mitigate this?

thanks,

Simon

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