Timo Sirainen wrote:
Well, check what OE6 is talking to Dovecot. Is it fetching headers or bodies for all messages? It should do that to only new messages.
Rawlog or some network sniffers could tell what exactly is happening. http://dovecot.procontrol.fi/bugreport.html#sniffing
Also is Dovecot really rebuilding the indexes all the time? How do you know? Try the in-memory indexes, at least then it's not rebuilding any indexes to disk.
actually it was just a tip. what is sure, if I stop dovecot the load fall down and there is no cpu load at all.
imap(lfarkas): May 21 12:20:01 Error: Corrupted index file /home/lfarkas/Maildir/.INBOX/.imap.index: index.next_uid (64) > uidlist.next_uid (63)
Hmm.. I was going to suggest trying 0.99.10-test, but I guess you're using it now? Looks like I have similiar error messages in my log :) Have to fix those.
this is the today morning cvs.
You didn't say how long this load problem has been going on, was it only recently or for longer now?
recently one or two week, but eg todays I see load around 8-9...
-- Levente "Si vis pacem para bellum!"