I have been using dovecot 1.0alpha4 + deliver/sieve in production for a few accounts (400'000). After testing 1.0.rc22 I decided to upgrade one of the imap servers... And... what a mess ! The server just gets unusable. I don't know why but with new release, it just overloads the system with I/O. It turns that with 1.0.rc22 I get 15Mo/s read on disk average, without any reason. What did really change ? How come a system (with a few thousand accounts) works perfectly and then with 1.0.rc22 gets unusable with a load approaching 300 ? If you have any ideas...
On Tue, 2007-02-20 at 09:53 +0100, Rene Luria wrote:> The server just gets unusable. I don't know why but with new release, it > just overloads the system with I/O. > It turns that with 1.0.rc22 I get 15Mo/s read on disk average, without > any reason. > What did really change ? How come a system (with a few thousand > accounts) works perfectly and then with 1.0.rc22 gets unusable with a > load approaching 300 ?Show dovecot -n output? What's your operating system? What filesystem? Does it do IMAP, POP3 or both? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20070220/f5273d3a/attachment.bin>
On Tue, 2007-02-20 at 09:53 +0100, Rene Luria wrote:> I have been using dovecot 1.0alpha4 + deliver/sieve in production for a > few accounts (400'000).How did you upgrade deliver/sieve? I guess you were before using the separate deliver binary from dovecot-sieve CVS tree. But did you upgrade to Dovecot's own deliver with cmusieve plugin? (again looks like dovecot -n doesn't print protocol lda {}..) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20070220/4bc5b36a/attachment.bin>