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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
