Return-Path: Delivered-To: apmail-incubator-lucene-net-user-archive@locus.apache.org Received: (qmail 3101 invoked from network); 17 Feb 2008 17:44:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Feb 2008 17:44:25 -0000 Received: (qmail 39976 invoked by uid 500); 17 Feb 2008 17:44:19 -0000 Delivered-To: apmail-incubator-lucene-net-user-archive@incubator.apache.org Received: (qmail 39948 invoked by uid 500); 17 Feb 2008 17:44:19 -0000 Mailing-List: contact lucene-net-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: lucene-net-user@incubator.apache.org Delivered-To: mailing list lucene-net-user@incubator.apache.org Received: (qmail 39939 invoked by uid 99); 17 Feb 2008 17:44:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Feb 2008 09:44:19 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=HTML_MESSAGE,HTML_OBFUSCATE_05_10,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of patrickng@jobsdb.com designates 202.45.130.13 as permitted sender) Received: from [202.45.130.13] (HELO mail.jobsdb.com) (202.45.130.13) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 17 Feb 2008 17:43:47 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C8718C.BCBB5D73" Subject: Index Search becomes very slow during index update Date: Mon, 18 Feb 2008 01:44:36 +0800 Message-ID: <4EC267A72E6B1A46A9CB5619737136080B4C9818@EXCLUSTER.jobsdb.global> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Index Search becomes very slow during index update Thread-Index: AchxjMNTVXRiXlfYRfSBR186bEbzHQ== From: "Patrick Ng" To: Cc: "Peter Chiu" , "Wing Fong" X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C8718C.BCBB5D73 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, Our company has been using Lucene.Net. Our index file size is small (<200MB), the number of document is small (<100000), and our searching is very fast (below 200ms). And we also have a service which updates (i.e. delete and add) documents in the index once every minute. What we found out is that whenever there is an update (frequency is 4-7 updates per second, come in burst of duration of 5-10sec once a minute), the searching time will in many cases increase to >1000ms. Sometimes it could go up to 5000ms! We have already looked through our code but couldn't find any obvious locking problem. Please note that we're also optimizing our index once every 10 minutes. Would really appreciate if anyone could give us some tips on what we should look at. Thanks, - Patrick ------_=_NextPart_001_01C8718C.BCBB5D73--