If mergeFactor is set to 2 and no optimize() is ever done on the index,
what is the impact on
1) the number opened files during indexing
2) the number of opened files during searching
2) the search speed
3) the indexing speed
??
HC
---
I would say, that over time, the number of files will grow. and continue
growing if you never perform
an optimize(). After some very adviceful mails from Erick i settled on a
mergeFactor of 30, and since I do the indexing in large batches, I perform
an optimize() only in the end of the indexi
The contrib/benchmark addition can help you characterize many of
these scenarios, especially if you write a DocMaker and QueryMaker
for your collection.
On May 8, 2007, at 5:30 AM, Stadler Hans-Christian wrote:
If mergeFactor is set to 2 and no optimize() is ever done on the
index,
what i
Hi,
- Original Message
From: Stadler Hans-Christian <[EMAIL PROTECTED]>
If mergeFactor is set to 2 and no optimize() is ever done on the index,
what is the impact on
1) the number opened files during indexing
OG: it will grow a little, but frequently go down as Lucene merges segments
