From java-user-return-37574-apmail-lucene-java-user-archive=lucene.apache.org@lucene.apache.org Sun Dec 07 12:28:01 2008 Return-Path: Delivered-To: apmail-lucene-java-user-archive@www.apache.org Received: (qmail 64121 invoked from network); 7 Dec 2008 12:28:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Dec 2008 12:28:01 -0000 Received: (qmail 62885 invoked by uid 500); 7 Dec 2008 12:28:06 -0000 Delivered-To: apmail-lucene-java-user-archive@lucene.apache.org Received: (qmail 62851 invoked by uid 500); 7 Dec 2008 12:28:06 -0000 Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: java-user@lucene.apache.org Delivered-To: mailing list java-user@lucene.apache.org Received: (qmail 62840 invoked by uid 99); 7 Dec 2008 12:28:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 Dec 2008 04:28:06 -0800 X-ASF-Spam-Status: No, hits=3.7 required=10.0 tests=DNS_FROM_OPENWHOIS,FORGED_HOTMAIL_RCVD2,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 07 Dec 2008 12:26:35 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1L9IjL-000241-DN for java-user@lucene.apache.org; Sun, 07 Dec 2008 04:27:23 -0800 Message-ID: <20880541.post@talk.nabble.com> Date: Sun, 7 Dec 2008 04:27:23 -0800 (PST) From: mimounl To: java-user@lucene.apache.org Subject: IndexWriter.flush performance MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: mimounl@hotmail.com X-Virus-Checked: Checked by ClamAV on apache.org Hello, In my application, I need to flush data each time a modification is made. So each time an entry is added in the lucene index we call IndexWriter.flush this way all data are secured on file system. We noticed that this operation is more and more time consuming while the size of the index raises. How can I tune the index to have a duration constant for the flush operation ? Before changing our logic for example flushing each "n" entries, I'd like to be sure that there isn't something I miss. I saw that the IndexWriter API changed in last version but our version is 2.3.1 that don't have for example the commit operation (and the flush method is deprecated). Thank you for your suggestions. -- View this message in context: http://www.nabble.com/IndexWriter.flush-performance-tp20880541p20880541.html Sent from the Lucene - Java Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org For additional commands, e-mail: java-user-help@lucene.apache.org