Byron Miller wrote:
For example i've been tweaking max merge/min merge and such and i've been able to double my performance without increasing anything but cpu load..
Smaller maxMergeDocs will cost you in the end, since these will eventually be merged during the index optimization at the end. I would just leave this at Integer.MAX_VALUE.
Larger minMergeDocs will improve performance, but by using more heap. So watch your heap size as you increase this and leave a healthy margin for safety. This is the best way to tweak indexing performance.
Larger mergeFactors may improve performance somewhat, but by using more file handles. In general, the maximum number of file handles is around 10-20x (depending on plugins) the mergeFactor. So raising this above 50 on most systems is risky, and the performance improvements are marginal, so I wouldn't bother.
Doug
