: Just to clarify - we do not optimize on the slaves at all. We only optimize : on the master.
that doesn't change anything about hte comments that i made before. it *really* wouldn't make sense to optimize on a slave right before pulling a new snapshot, but it still doesn't make any more sense to optimize on a master right before doing some updates and then pulling a new snapshot. my second comment also still applies: a snappull after an optimize is always going to be involve more churn on the disk... : > : We do optimize the index before updates but we get tehse performance : > issues : > : even when we pull an empty snapshot. Thus even when our update is tiny, : > the : > : performance issues still happen. : > : > FWIW: this behavior doesn't make a lot of sense -- optimizing just : > before you are about to make updates/additions ot your data, is a complete : > waste. the main value in optimizing your index is that you have one : > segment, as soon as you add a docment that changes. : > : > the other thing to keep in mind is that an optimized index is a completley : > new segment as a new file with a new name, so there is going to be added : > overhead on the slave machines as the OS purges the old index files and : > replaces them with the new optimized index files -- more overhead then if : > you had just done your additions w/o optimizing first. -Hoss
