Bug 292345 - Viewing next message with IMAP often takes a long time after skipping some
Summary: Viewing next message with IMAP often takes a long time after skipping some
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.8
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-24 18:20 UTC by Alex Richardson
Modified: 2015-09-09 21:13 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Richardson 2012-01-24 18:20:10 UTC
Version:           4.8 (using Devel) 
OS:                Linux

I usually read all my mails on my (googlemail)-IMAP Account by just pressing Num+ to get the next message.

When I press Num+ again before the next message has loaded (e.g. because the whole thread doesn't interest me) at least once it often happens that the message which is now selected  takes a long time to load (1 minute or more if the number of skipped messages is large).

I noticed that akonadi_imap_resource was writing at ~40-80 KByte/s for a while, every now and then mysqld would write ~800KByte/s for 1-2 seconds.

Maybe it is an issue with marking all the skipped messages as read, because in the UI they stay unread until the currently selected message actually loads.

Maybe akondi is trying to fetch the messages from the server and does not continue to the next until the current one is fetched. If that is the case IMO it should just mark those messages as read and not bother fetching them at all.

Reproducible: Sometimes

Steps to Reproduce:
1. Open an IMAP folder in KMail which has some unread messages
2. Press next message a few times
3. wait until the selected message is displayed in KMail

Actual Results:  
It takes quite a long time until the desired message is shown. I am not sure if it is proportional to the number of skipped messages.

Expected Results:  
The selected message should appear within a short time (preferably less than 2 seconds)

OS: Linux (x86_64) release 3.1.0-1.2-desktop
Compiler: gcc
Comment 1 Alex Richardson 2012-03-09 20:10:37 UTC
It seems to be fine now with 4.8.1 after I disabled Nepomuk.
Maybe it has something to do with the akonadi_nepomuk_feeder
Comment 2 Martin Steigerwald 2015-09-09 21:13:00 UTC
Thank you Alex for your report. It is about a version of KMail which uses Nepomuk and is unmaintained. Thus closing. If you still see performance issues please open new reports. But please follow the following guide lines to avoid unnecessary work for the developers:

- Ideally test with KDEPIM and Akonadi 15.08. It contains some performance
improvements like the binary protocol.

- Otherwise at least use KDEPIM 4.14.10 and newest Akonadi 1.13 you can get as
it already contains some performance improvements.

- If you can wait, please retest with KDEPIM and Akonadi 15.12 once they become
available for you. Akonadi 15.12 will contain *massive* performance
improvements implemented by Dan due to new database indexes, optimized queries
and leveled file_db directory. All of these are in master already, so if you
dare use kdesrc-build to compile KF5, kdepim and kdepim-runtime. I am using
this currently and it basically moves the bottleneck to KMail (slow threading
for example). It is a *huge* improvement.

Thank you and greetings from KDE Randa Meetings,
Martin