lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael McCandless <luc...@mikemccandless.com>
Subject Re: Performance of never optimizing
Date Wed, 05 Nov 2008 16:23:03 GMT

Tomer Gabel wrote:

> Since you're using an 8-core Mac Pro
> I also assume you have some sort of RAID setup, which means your  
> storage
> subsystem can physically handle more than one concurrent request,  
> which can
> only come into play with multiple segments.

This is an important point: a multi-segment index naturally allows for
utilizing IO concurrency with multiple searches against a single
IndexReader.  It's actually a reason against optimizing, strangely
enough.

However, as of Lucene 2.4 there's a new directory impl NIOFSDirectory
that on Unix should eliminate that bias (on Windows it will be slower,
due to problems with Sun JREs impl of nio APIs specific to Windows).
Also, you can and should open read-only IndexReaders since that also
removes further internal locking.  If you do test these please report  
back on
what difference they made...

Mike

---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


Mime
View raw message