lucenenet-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Woolum" <cwoo...@moonvalley.com>
Subject RE: Lucene.Net 2.9 Uses Single Processor under Stress
Date Wed, 19 Jan 2011 21:38:38 GMT
I didn't think Lucene has built in threading using a regular
Indexsearcher or Indexreader. Wouldn't this be a problem with threading
in your Lucene implementation? This is just as far as I knew... Somebody
please correct me if I am wrong.

Chris



-----Original Message-----
From: Frank Yu [mailto:frank.yu@farpoint.com] 
Sent: Wednesday, January 19, 2011 1:16 PM
To: lucene-net-user@lucene.apache.org
Subject: Lucene.Net 2.9 Uses Single Processor under Stress 

Hi All,

I met a strange situation that the Lucene.Net used only 1 processor on a
quad dual-core processors machine when the search load exceeded a
certain threshold (i.e., 35 searches per second). It took a few minutes
before the load got distributed over all processors. When the load was
below the threshold (i.e., 20 searches per second), all processors got
used evenly. 

The used Lucene.net is v2.9 and the index size is about 4GB with 15
millions of documents. There was no index update and the load was search
only without any index update. 

Has anyone seen this kind of behavior before?

Thanks a lot,

Frank



Mime
View raw message