The compound file format used to have more issues with multi-threaded contention when searching, but these have been fixed. When the underlying directory implementation is non-blocking (NIO), there shouldn't be a difference for searching.
I know that improvements have been made on the indexing side as well, but I'm not sure what the penalty will be. Anyone care to run a quick test? -Yonik http://www.lucidimagination.com On Mon, Mar 9, 2009 at 10:51 AM, Peter Wolanin <peter.wola...@acquia.com> wrote: > Trying to set up a server to host multiple Solr cores, we have run > into the issue of too many open files a few times. The 2nd ed "Lucene > in Action" book suggests using the compound file format to reduce the > required number of files when having multiple indexes, but mentions a > possible ~10% slow-down when indexing. Are there any other down-sides > to this? Seems to work by just changing this line in solrconfig.xml: > > <mainIndex> > <!-- options specific to the main on-disk lucene index --> > <useCompoundFile>true</useCompoundFile> > > -- > Peter M. Wolanin, Ph.D. > Momentum Specialist, Acquia. Inc. > peter.wola...@acquia.com >
