I just want to point out that I don't consider these bottlenecks to be an
issue. This is exactly where I'd expect to see hotspots from the profiler,
and the overall performance of Lucene search is still stunning.
Peter
On Wed, Jun 24, 2009 at 10:13 AM, Peter Keegan wrote:
> Our biggest bottlen
Our biggest bottleneck in searching is in a custom scorer which calls
AllTermDocs.next() very frequently. This class uses Lucene's own BitVector,
which I think is already highly optimized. Farther down in the list are
DocSetHitCollector.collect() and FieldSortedQueue.insert(). For indexing,
the mai
On Tue, 9 Jun 2009, Vico Marziale wrote:
: highly-multicore processors to speed computer forensics tools. For the
: moment I am trying to figure out what the most common performance bottleneck
: inside of Lucene itself is. I will then take a crack at porting some (small)
: portion of Lucene to CUD
Hello all. I am new to Lucene as well as this list. I am a PhD student at
the University of New Orleans. My current research in in leveraging
highly-multicore processors to speed computer forensics tools. For the
moment I am trying to figure out what the most common performance bottleneck
inside of
