[Bug 307058] KMail reacts sluggish but keeps telling my by system notification that it is not broken

[Marcel Wiesweg]

https://bugs.kde.org/show_bug.cgi?id=307058

--- Comment #1 from Marcel Wiesweg <marcel.wiesweg at gmx.de> ---
Created attachment 74085
  --> https://bugs.kde.org/attachment.cgi?id=74085&action=edit
KDE system monitor CPU usage

A good part of the behavior described above seems to be due to marking a mail
as read being extremely CPU intensive in the backends.
I use "+" to read the next unread mail. For a) one mail (first peak) b) four
mails (second peak) c) 15 mails (long plateau) being such marked as read the
CPU usage is depicted in the attachment.
The involved processes are mysqld (~60%), kontact and the mixelmaildir
resource.
As you see, marking 15 mails as read results in about 15 secs of 100% dual core
CPU usage.
If I am patient and give it the time it needs, the peculiarities described
above do not appear.

-- 
You are receiving this mail because:
You are the assignee for the bug.