[Kde-pim] akonadi and continual disk activity

[Andras Mantia]

D. R. Evans wrote:

> Andras Mantia said the following at 11/16/2012 10:23 AM :
>> D. R. Evans wrote:
>> 
>>> Andras Mantia said the following at 11/16/2012 08:30 AM :
>>>> D. R. Evans wrote:
>>>>
>>>>> Now that I've populated kontact with two calendars and one contact
>>>>> file, akonadi (and/or mysql jobs spawned by it -- the precise culprit
>>>>> changes moment-by-moment according to iotop) is thrashing the disk for
>>>>> hours on end.
>>>>>
>>>>> How do I make it stop doing that and behave properly? The behaviour
>>>>> started sometime overnight. It was fine yesterday.
>>>>
>>>> Probably the newly created data is being indexed, but this could be
>>>> just a guess, unless you find out which process itself is doing it.
>>>
>>> How do I discover which process is responsible?
>>>
>>> There are two remote calendars, and about 3,000 contacts in the address
>>> book, which doesn't seem like it should take very long at all to
>>> incorporate into any kind of PIM system. Minutes of minor activity
>>> perhaps, but not hours of continual thrashing.
>> 
>> Well, top, iotop, turn off nepomuk, turn off individual akonadi agents.
>> 
> 
> I'm sorry ... I'm just an increasingly frustrated user trying to get back
> to having a usable PIM. 

On a developer list I expect some knowledge about the system. :)

> What is an "akonadi agent" and how would I turn
> them off individually?

Agent == the application actually gathering the data. The interface towards 
your real data. E.g the POP3 agent (resource) downloads the mail from a POP3 
server, the IMAP agent from an IMAP server, the Nepomuk Feeder agent indexes 
the downloaded mails for searching, the various calendar/addressbook agents 
deal with the respective data. All of them are in separate process. In top 
they show up as akonadi_XXX_agent or akonadi_XXX_resource .

> 
> I'm truly sorry, but I didn't expect to need to know any of this stuff
> just to maintain calendars and contacts, so please walk me carefully
> through *exactly* what I need to do in order to provide some more useful
> information.
> 
> FWIW, I just truned akonadi back on. Instantly the hard drive started
> thrashing, and the top five I/O processes are all mysqld processes that
> have "akonadi" in their parameter strings.

When you see the problem try to:
- run top and see what process is busy
- run iotop and see what process is causing high IO
- run akonadiconsole, go onto the Agent tab and turn off (Toggle them 
offline) agents one-by-one and check if the problem goes away. Do not remove 
them, unless you are ready to add them back again
- go to system settings and turn off the semantic desktop search (nepomuk)

See what helps from the above.

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