[Kde-pim] Akonadi mail performance outlook

Martin Steigerwald Martin at lichtvoll.de
Fri May 2 10:07:19 BST 2014


Am Freitag, 2. Mai 2014, 10:19:15 schrieb Martin Steigerwald:
> Am Donnerstag, 1. Mai 2014, 21:50:40 schrieb GEO:
[…]
> > I am using Akonadi for my mail setup now more intensively than every
> > before
> > and have an mail account with over 10 000 mails atm. This is enough to see
> > some performance issues associated with Akonadi.
[…]
> > Here are my top 3 (in the following folder sync means when you have just
> > created your account and you click a folder):
> > 
> > 1.) When configuring an imap account (gmail in my case) and you click a
> > folder in kmail, the sync will begin. (No special settings, just created
> > the account with the account wizard). If you click another folder now,
> > nothing happens, it will wait till the initial folder is completely
> > synced.
> > This is not exactly asynchronous and should be addressed.
> 
> I can confirm that for sync operations in a huge maildir resource which is
> filled by POP3 agent. A sync operation blocks out KMail for minutes. Which
> doesn´t match one of the design goals for Akonadi.
> 
> I wanted to look into this further and I actually had a look at the source.
> All I could find there where some calls about synchronize collection tree
> with a comment that this may not be needed here, but that this wouldn´t
> matter. As I didn´t yet follow read up / understood what this call does and
> had different things to do… I didn´t get follow up on this.

I reported two bugs about it:

Bug 334206 - While maildir resources synchronrizes a folder KMail blocks on 
switching to a different folder 
https://bugs.kde.org/334206

Feel free to add this one for IMAP resource. I didn´t see this with latest 
Akonadi git tough I think, so better check with Akonadi git.


Bug 334209 - synchronizes folder contents during runtime needlessly
https://bugs.kde.org/334209

I haven´t been able to reproduce this one consistently tough. It hapens that 
Akonadi synchronizes folder contents during runtime needlessly. As I found 
akonadi maildir resources watches folder contents with inotify. So during 
runtime of Akonadi which is days or even weeks on my laptop, Akonadi IMHO has 
no business to ever synchronize its database contents with the filesystem 
content. The files will still be there as long as the filesystem works 
correctly.

I still plan to find out exactly when Akonadi server / maildir resources 
triggers a resync and *why* it does so. I did not yet understand enough of the 
code to know as to what function to look for exactly.


Akonadi is easy to compile:

- git clone git://anongit.kde.org/akonadi
- cd akonadi
- mkdir build
- cd build
- cmake ..
- install missing build deps from package management
- make -j4
- sudo make install -j4

Adapt -j option to amount of cores you want to use.

cmake doesn´t to an uninstall target, but install_manifest.txt contains a list 
of files installed.

sudo cat install_manifest.txt | xargs echo rm

thus removes those files again if you remove the echo from above command line.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/


More information about the kde-pim mailing list