Mailing-List: contact lucene-net-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: lucene-net-user@lucene.apache.org
Received-SPF: pass (nike.apache.org: domain of digydigy@gmail.com designates
 209.85.214.48 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=from:to:references:in-reply-to:subject:date:message-id:mime-version
         :content-type:content-transfer-encoding:x-mailer:thread-index
         :content-language;
        b=lq7JKSqnwKAS3kgMxHlwQfvyT3pjV0xacJQ2+h1DTDjuIB26V8FXsyLgfRwl0Unq/C
         ev+wu7s9h15Idbld6GtigKCfbJg1lJ5s30RAvwdgmcKAWl+j0z+18CxMfbg1pHaXzGpi
         OvlMgKbJHkSVTTM6WNs88JKAA1RX+lKfarRQE=
From: "Digy" <digydigy@gmail.com>
To: <lucene-net-user@lucene.apache.org>
References: <00cf01cbb8f6$485b7510$d9125f30$@yu@farpoint.com>
 <135731.38588.qm@web33401.mail.mud.yahoo.com>
 <00bb01cbbbf0$691bb600$3b532200$@yu@farpoint.com>
In-Reply-To: <00bb01cbbbf0$691bb600$3b532200$@yu@farpoint.com>
Subject: RE: Thread Contention in Lucene.Net 2.9
Date: Mon, 24 Jan 2011 20:58:42 +0200
Message-ID: <001d01cbbbf8$b90cabd0$2b260370$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Thread-Index: Acu5hqhEof5jBLDuSr2Oz6jXkpbJtACZ/LRAAAJaZ0A=
Content-Language: tr

If you don't update the index, then why don't you use a single instance of
IndexSearcher throughout your app instead of reopening the IndexReader?

DIGY

-----Original Message-----
From: Frank Yu [mailto:frank.yu@farpoint.com] 
Sent: Monday, January 24, 2011 7:59 PM
To: lucene-net-user@lucene.apache.org
Subject: Thread Contention in Lucene.Net 2.9

Hi All,

I am using the Lucene.Net v2.9. Under the heavy load (search only without
any index update), there were a lot of thread contentions. Does the Lucene
use the locks even for the read-only search? Any suggestion for which
resource caused the thread contentions?

Thanks a lot,

Frank