Re: Possible akonadi problem?
Am Freitag, 23. Januar 2015, 09:54:10 schrieb Martin Steigerwald:
> On Donnerstag, 22. Januar 2015 22:11:37 CEST, Martin Steigerwald wrote:
> > Am Freitag, 23. Januar 2015, 07:17:13 schrieb Dmitry Smirnov:
> >> Hi Brad,
> >>
> >> On Fri, 2 Jan 2015 11:28:53 Brad Alexander wrote: ...
> >
> > Thank you very much, I will try this. And see whether it helps with
> > these upstream bugs:
> >
> > [Akonadi] [Bug 338402] File system cache is inneficient : too many
> > file per directory
> >
> > Bug 332013 - NFS with NetApp FAS: please split payload files in
> > file_db_data into several directories to avoid reaching maxdirsize
> > limit on Ontap / WAFL filesystem
> >
> > Bug 341884 - dozens of duplicate mails in
> > ~/.local/share/akonadi/file_db_data
> >
> >
> > I bet it may help with the first two, but third one might be another
> > bug.
> >
> >
> > Right now locally after the last akonadictl fsck I only have
> > from 4600 after
> > the fsck to 4900 files now in my private setup with still is
> > mostly POP3 just a
> > 30 day limited IMAP for the Fairphone and as a backup when I
> > accidentally mess
> > up with something locally. It really seems Akonadi is more snappy
> > since the fsck. I have lots more files in there.
> >
> > I also bumped innodb_buffer_pool_size but didn´t see that much of a
> > change, what helped most with MySQL load is to use Akonadi git 1.13
> > branch with database performance improvement.
> >
> > I now implemented the treshold size change you suggested and
> > did another fsck
> > and vacuum.
>
> *beware this is partly a rant, but I think a well founded one*
>
> In the end it I had mysqld excessively writing 150-300 MiB for about 15
> minutes or more, sure it wrote the *complete* size of the database
> several times. I do have an mysqld where it complains about not being
> able to get locks and suggesting that a second instance might be
> running. I found this later one.
>
> I don´t think it had to do with the change you suggested, but with
> another problem. I found it often enough that after akonadictl stop and
> akonadictl status telling it is actually stopped, mysqld was still
> running. I usually check this and do SIGTERM on it waiting for it to
> end. But I didn´t yesterday.
>
> After a long time of writes I sigkilled the mysqld process in order to
> end the excessive writes.
>
> I tried to recover from backup, but it didn´t work out. At one time I
> created a second maildir resource and even after making sure I had
> everything of ~/.config/akonadi from backup and also making sure there
> are no other files in it with rsync --del and same for
> ~/.local/share/akonadi and even after deleting
> akonadi_maildir_resource_1rc from
> ~/.kde/share/config it insisted on having a maildir resource 1 today and
> it filled database and file_db_data with the results of scanning my
> million of mails again.
After about half a day of waiting, and wanting to wipe off Akonadi from my
system for good, re-importing filter I am almost back to some sanity.
I am really looking forward to a replacement of Akonadi. I think it needs
one.
One with simplicity, robustness and performance as in only use as much
resources as the task at hand really needs in mind.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
Reply to: