Found a mistake in my reponse...when I was talking about max merge docs,
I meant max buffered docs. If your going to optimize anyway, the key
setting appears to be max buffered docs, and I have yet to see the merge
factor affect anything (again, only if you optimize). Oddly, performance
seems t
You may find contrib/Benchmark useful in your testing. Doron Cohen
has added a nice framework for scripting benchmarking tests.
-Grant
On Feb 11, 2007, at 12:14 PM, Mark Miller wrote:
Not sensible at all. First, a merge above something like 90 most
likely never makes since. Second, I have
Not sensible at all. First, a merge above something like 90 most likely
never makes since. Second, I have done some testing and my results show
that if you optimize the index after loading, the merge factor really
doesn't matter so keep it at 10 (I never used a max merge docs below 50.
100 work
tanuwidjaja [mailto:[EMAIL PROTECTED]
Sent: 11 February 2007 15:44
To: java-user@lucene.apache.org
Subject: about merge factor
Hi all,
I just wondering wheter is it sensible and possible if I have 660,000
documents to be indexed,I set the merge factor to 660,000 instead of the
default value 10
Hi all,
I just wondering wheter is it sensible and possible if I have 660,000
documents to be indexed,I set the merge factor to 660,000 instead of the
default value 10 (...and this means no merge while indexing) and later after
closing the index,I use the IndexWriter to optimize/merge t
