lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Beard, Brian" <Brian.Be...@mybir.com>
Subject RE: performance feedback
Date Thu, 10 Jul 2008 15:13:45 GMT
Currently the default setting is being used with our setup, so
autoCommit is true. I'll set this to false to see if it improves.

Question: If autoCommit is false, does this apply to optimization also,
so that during an hour long optimization that gets killed in the middle,
will the index be in the left in the initial state before optimization
started?

-----Original Message-----
From: yseeley@gmail.com [mailto:yseeley@gmail.com] On Behalf Of Yonik
Seeley
Sent: Wednesday, July 09, 2008 12:06 PM
To: java-user@lucene.apache.org
Subject: Re: performance feedback

On Wed, Jul 9, 2008 at 11:35 AM, Beard, Brian <Brian.Beard@mybir.com>
wrote:
> I will try tweaking RAM, and check about autoCommit=false. It's on the
> future agenda to multi-thread through the index writer. The indexing
> time I quoted includes the document creation time which would
definitely
> improve with multi-threading.
>
> I'm doing batch updates of up to 1000 a pop, and closing and
re-opening
> the IndexWriter in between.

autoCommit=false will definitely help, and there is normally no reason
not to use it.
Bigger batches (or a single batch) will also help indexing speed.  A
single IndexWriter session can now avoid copying stored fields on
segment merges.

-Yonik

---------------------------------------------------------------------
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


Mime
View raw message