Bug 352604

Summary:	(Regression?) kMail 5.0.x: kMail always "syncs" IMAP folder whenever it is opened, even if its unchanged
Product:	[Applications] kmail2	Reporter:	Gunter Ohrner <kdebugs>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version:	5.5.2
Target Milestone:	---
Platform:	Neon
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Gunter Ohrner 2015-09-12 08:07:50 UTC

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

Comment 1 Gunter Ohrner 2015-09-12 09:21:13 UTC

Mh, this problem seems to affect the Sent mail folder *only*?

Is there anything which could cause this in a folder-specific way? Is there any way to eg. refresh/rebuild this folder's management information or indices to check if this fixes the observed behaviour? I could not find anything related in the folder's properties / maintenance dialog / tab...

Comment 2 Denis Kurz 2017-06-23 20:18:49 UTC

This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.

Comment 3 Gunter Ohrner 2017-06-25 09:06:16 UTC

Unfortunately, this is still current as of the versions listed as follows, no improvements whatsoever.

KMail
Version 5.5.2

KDE Frameworks 5.35.0
Qt 5.9.0 (kompiliert gegen 5.7.1)
Das xcb Fenstersystem

Comment 4 Justin Zobel 2022-11-06 09:25:23 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 5 Bug Janitor Service 2022-11-21 05:12:14 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 6 Bug Janitor Service 2022-12-06 05:18:46 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!