I set mine to 300, and the spikes just go to every 5 minutes instead of every 2 minutes (although there is a seperate but smaller spike, still, every 2 minutes). Making the interval larger I understand, since there is a contention between two different processes for the same thing (probably disk i/o and cpu).
But I think the real problem is, why does it use up that much cpu. I believe, on some machines the task runs much faster than others. Maybe some type of library incompatability, or possibly inefficient code. I think its probably some type of incompatability and its timing out. Anyway, it seems like a very high load for a new zimbra installation with no accounts, outside of the defaults. |