[Kde-pim] Akonadi: single database design mistake?

[Martin Steigerwald]

Am Donnerstag, 2. Mai 2013, 12:34:24 schrieb Martin Steigerwald:
> Am Montag, 29. April 2013, 16:37:41 schrieb Milian Wolff:
> > On Monday 29 April 2013 07:30:27 bhlevca wrote:
> > > Andras Mantia-2 wrote
> > >
> > > 
> > >
> > > > Point out the design problem and than we can talk about something,
> > > > without
> > > > it, sorry, this not more, but the usual ranting without supporting
> > > > evidence
> > > > of what is the problem...
> > >
> > > 
> > >
> > > Why did I expect a decent answer? I don't know, but this is just another
> > > rude, mindless email answer defending a bad decision and refusing to see
> > > that everyone is complaining about KDEPIM.
> > >
> > > 
> > >
> > > If you want a supporting evidence like code lines, you know very well
> > > that
> > > it is very hard to give and would take time. I would rather rewrite the
> > > whole thing if I had the time.
> > >
> > > 
> > >
> > > But,  If you take the time and cool down as I initially suggested, you
> > > will
> > > notice that in my first message I suggested alternatives (the notmuch
> > > mail
> > > approach) and I pinpointed the culprit: The large behemoth central
> > > database
> > > based design that does everything and is the bottleneck. And I repeat,
> > > although it is a nice idea, its complexity will bring you down if it
> > > didn't
> > > already.
> >
> > 
> >
> > Considering that I did a bunch of profile runs on kdepim, I rarely, if
> > ever,  saw a bottleneck in the database. Mysqld is also running just fine.
> 
> I beg to differ here. And I think I can prove it (via atop logs):
> 
> [Akonadi] [Bug 319208] New: KMail unresponsive for minutes after POP3 
> retrieval and filtering with high MySQL load for minutes
> 
> https://bugs.kde.org/show_bug.cgi?id=319208
> 
> (This is with full text mail indexing *disabled*)
> 
> 
> And yes, I have the impression that raising innodb_buffer_pool_size from an 
> IMHO way to low 80M for decently sized mail accounts to 500M, seemed to
> help.
> 
> Its still to early to say for sure, but it seems to be more responsive. In
> the  next days, especially on retrieving POP3 mails accumulated over the
> night I can say more.
> 
> I will try for some days and probably reduce it in steps by 100 MiB as long
> as  performance is still okay for this speed machine (see below).

I think raising the limit to 500M helped a bit, but what helped even more is:

Go to account settings and then set the maildir resource to update on new 
start instead of manual check. This way when I click the retrieve mail button 
just the POP3 resource is triggered. And the maildir resource just takes the 
mail, but doesn´t start a full synchronisation.

I wonder why the maildir resource is set to synchronize by manual trigger at 
all.

I will add this to the bug report.

-- 
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/