: One technique to control commit times is to do automatic commits: you : can configure a core to commit every N seconds (really milliseconds, : but less than 5 minutes becomes difficult) and/or every N documents. : This promotes a more fixed amount of work per commit.
...but increaseing commit frequency only really helps you if the slowdown you are seeing is coming from the actaul commit -- if it's coming from really resource intensive cache warming that chews up all the CPU then it can just make the problem worse -- likewise, if you don't have any warming, the perception of "slow/stoped queries during/after commit" can sometimes come from time spent initializing FieldCaches (particularly if there is one or two fields that almost all queries sort on ) the long and short being: performance issues can be caused by a great many differnet things, so you really need to figure out what exactly is going on during these "slow" periods in order to dtermine the best way to deal with it. -Hoss
