This forum has been archived. All content is frozen. Please use KDE Discuss instead.

kmail using insane amount of CPU cycles.

Tags: None
(comma "," separated)
User avatar
georgelappies
Registered Member
Posts
22
Karma
0
OS
Hi all

This relates to Kubuntu 13.04. It is a clean install into a clean /home folder. When I launch kmail the CPU usage of the virtuoso-t process increases by a huge amount.

I have an i5 laptop and the usage of that process before kmail is launched is below 1% a few moments after kmail is launched the process usage shoots up to 150%+ (so atleast one and a half cores are being maxed by the virtuoso-t process...). If this settled after a few hours it would be ok, but it doesn't seem to settle down and there is no clear way of seeing what is being done or if it is only a zombied thread inside virtuoso.

Being a laptop this of course completely destroys battery life. The sad thing is that I mainly use the laptop for email (due to it being mobile) while on the road and as such needs the auto complete of contact's email address and the semantic features.

Is there a way to determine if this process is indeed zombified and looping or if it is actually indexing the email. But what confuses me is why would nepomuk only want to index emails when kmail is open? Surely it has access to the local email headers in the same way kmail has??

Kind regards,

George
User avatar
einar
Administrator
Posts
3402
Karma
7
OS
You can enable idle detection, ensuring that mail is indexed only when your computer is idle. Open "akonadiconsole", locate the "Nepomuk Feeder" and click on Configure. Untick "disable idle detection" and set your desired idle time for indexing. Then confirm with OK.

The reason why mails are only indexed when KMail is open may lie in how you set it up: do you have accounts set as "go offline at KMail shutdown"?


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]