In my own Solr 1.4, I am pretty sure that running an index optimize does
give me significant better performance. Perhaps because I use some
largeish (not huge, maybe as large as 200k) stored fields.
So I'm interested in always keeping my index optimized.
Am I right that if I set mergeFactor to '1', essentially my index will
always be optimized after every commit, and actually running 'optimize'
will be redundant?
What are the possible negative repurcussions of setting mergeFactor to
1? Is this a really bad idea? If not 1, what about some other
lower-than-usually-recommended value like 2 or 3? Anyone done this?
I imagine it will slow down my commits, but if the alternative is
running optimize a lot anyway.... I wonder at what point I get 'break
even' (if I optimize after every single commit, clearly might as well
just set the mergeFactor low, right? But if I optimize after every X
documents or Y commits.... don't know what X/Y are break-even).
Jonathan
