[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: severe load on imap sever by kmail



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am Mittwoch, 23. Juni 2004 19:30 schrieb Courtney Sherman:
> > Maybe kmail does server side filtering and your mailboxes are very large,
> > so that is takes a lot of time and ressources?
AFAIK courier-imap does not support server side filtering, and neither does 
KMail (even though there is an option in the config, it does not do anything 
right now), so that cannot be the problem.

> If it does, it does it automatically.  The slowdowns occur on a fresh
> install without ever having enabled any filtering.  This is not a new
> problem.  Every version of kmail I have tried (starting with the one in
> KDE 3.0) acts the same way.  The problem does seem to scale with the
> size of the directory, but is severe enough that kmail is largely
> intolerable for IMAP.
I am using KMail for IMAP on folders containing more than 10000 messages, and 
it all is very fast (IMAP Server is local, so KMail just goes as fast as it 
can). Though I do use Cyrus IMAPd, not Courier. Maybe there is some bad 
interaction between KMail's use of the IMAP protocol and some inefficiency in 
Courier IMAPd. Maybe KMail wants to reindex the folder and does it in a way, 
where Courier becomes heavily loaded.

Searching http://bugs.kde.org for "kmail imap slow" shows several complaints 
in that direction. Also there are some (admittedly simple) hints, what can 
cause some kinds of slowdown (IMAP store on NFS, Thrash Folder not on IMAP 
server, but local...)

Does KMail do any network transfers while it is stuck (is it downloading large 
amounts of data, or sending a large number of commands to the server?)

Patrick
- -- 
Patrick Dreker

GPG KeyID  : 0xFCC2F7A7 (Patrick Dreker)
Fingerprint: 7A21 FC7F 707A C498 F370  1008 7044 66DA FCC2 F7A7
Key available from keyservers
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA2cepcERm2vzC96cRApB8AJ4revU2sSr88hk1lFBP3SYgtayLGwCdHSVt
JUfqEjqZ/8RNmv0vZZVf00M=
=jTv8
-----END PGP SIGNATURE-----



Reply to: