[Akonadi] [Bug 325253] New: akonadi (kontact) becomes slow and unresponsive after some time

[Martin Tlustos]

https://bugs.kde.org/show_bug.cgi?id=325253

            Bug ID: 325253
           Summary: akonadi (kontact) becomes slow and unresponsive after
                    some time
    Classification: Unclassified
           Product: Akonadi
           Version: 4.11
          Platform: Kubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: kdepim-bugs at kde.org
          Reporter: martin.tlustos at gmail.com

I know this is a very unspecific bug report, but maybe someone can point me in
the right direction... ;-)
My akonadi setup is as follows:
3 dimap accounts, sending over smtp and saving sent messages in imap folders
/sent
1 DAV resource with 1 caldav collection (5 calendars, 4 of them shared) and 1
carddav collection (2 addressbooks, one is a shared one)
2 ical resources that point to the /tasks subfolders on the same server where
my imap and my dav resources point to (but somehow the dav resource does not
recognize the tasks, so I had to add them as ical resources).
Google Addressbook
Google Calendar
a local backup folder for archiving my older mail with subfolders for each year
(going back three years, with a total of about 10.000 emails in all subfolders
and of course local contacts, local mail folder, local notes, search,
invitations, mail indexer, tags,  etc...

RAM Memory consumption is as follows:
mysqld ~68MB
google-calendar ~35mb
google contacts ~32mb
mailfilter ~28mb
archivemail-agent ~26mb
sendlater ~26mb
akonadiserver ~13mb
nepomuktag ~11mb
and the others below 10mb,

36 processes in total (not counting akonadiconsole and akonaditray).

After working with emails in my imap accounts for a while, it starts to become
slow - it takes longer to open emails, to send emails etc. opening
akonadiconsole shows that sometimes, but not always, the email indexer is
working. Most of the time all resources are said to be "ready".

As long as the email indexer runs, virtuoso-t uses 99% of my cpu.

Sometimes it takes minutes to send an email (o.k., it has multiple recipients,
but still)...

Any hints? As it is right now I can't really work with it, but the other
clients there are are not up to par with it...


Reproducible: Always

-- 
You are receiving this mail because:
You are the assignee for the bug.