Thanks Mike,
This is running on Hotspots VM (on unix) the JVM has 24 GB of max heap.
Moving to Lucene 4.X is not an easy option because for us Lucene has shipped
as part of the Sterling 9.0 product if we upgrade part of the product we
would have to give away support.
One of my coworkers had
-threaded.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
-Original Message-
From: RameshIyerV [mailto:rameshiy...@hotmail.com]
Sent: Monday, July 22, 2013 11:15 AM
To: dev@lucene.apache.org
Subject: Re: Contentions observed
Uwe, we do not have the flexibility to change the implementation to user
MMapDirectory, lucene implementation is core to the Sterling 9.0 product
(and ships with it).
On heap, the box has 250+ GB, our application's (2) is using close to 68.
Also the application internally uses ehcache to cache
Lucene 2.4.x is quite ancient by now ...
FSDirectory.FSIndexInput is single-threaded in seeking/reading bytes,
which I think explains your 1 and 4. Try using MMapDirectory, if you
are using a 64 bit JVM or if your index is tiny. Newer Lucene
versions also have NIOFSDirectory, which is
