[kmail2] [Bug 352604] New: (Regression?) kMail 5.0.x: kMail always "syncs" IMAP folder whenever it is opened, even if its unchanged

[Gunter Ohrner]

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

            Bug ID: 352604
           Summary: (Regression?) kMail 5.0.x: kMail always "syncs" IMAP
                    folder whenever it is opened, even if its unchanged
           Product: kmail2
           Version: unspecified
          Platform: Kubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: kdepim-bugs at kde.org
          Reporter: kdebugs at CustomCDROM.de

As far as I can say, I've not had this problem with kMail 4.14.x (or any older
version) before and it's pretty annoying:

I'm using kMail to access a normal IMAP account. kMail and the IMAP server are
running on the same machine, the IMAP server used is a Dovecot 2.2.9. All data
is on a fast SSD and the system is a dualcore Core i7 Ivy Bridge with 3 GHz
with 12 GB RAM and plenty of it still free.

Whenever I switch folders, kMail resynchronizes the folder, even if it
definitely has not changed. At least somtimes, kMail even synchronizes a folder
*twice* after opening it once, causing the delay to double until mails in this
folder can be accessed.

In kMail 4.14.x and before and if I remember correctly, the folder was only
resynchronized if its contents changed since the last visit, eg. new mails had
been dropped there. Additionally, IIRC synchronization was only ever done once
per opening a folder.

Due to an unresolved severe performance regression introduced in kMail or
Akonadi 4.14 (see bug #338571), this causes kMail or Akonadi to hammer the
local MySQL server used as the Akonadi backend and takes (felt) ages for larger
folders.

So in case I eg. switch (what I do quite often) to my IMAP "Sent" folder which
contains about 37000 messages, I always have to wait a whole minute until I can
access e-mails in it (two sychronizations, each taking about 30 seconds).
During that time, MySQL takes quite a bit of CPU but especially writes data
like mad...

Is there anything which could be done to require the sychronization frequency?
And I still hope the original bug #338571 performance regression in Akonadi
will be tackled one day...

Reproducible: Always

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