Bug 305966 - changing message state leads to 2-3sec 40% CPU abuse by virtuoso-t
Summary: changing message state leads to 2-3sec 40% CPU abuse by virtuoso-t
Status: RESOLVED INTENTIONAL
Alias: None
Product: kmail2
Classification: Applications
Component: misc (show other bugs)
Version: 4.9.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-29 07:02 UTC by Anders Lund
Modified: 2015-01-06 20:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anders Lund 2012-08-29 07:02:30 UTC
With mail indexing enabled, I can search my mail. But the cost is high, looking at CPU usage and in turn battery life. When any attribute of a mail is changed, enough CPU is used to start the fan :0

This includes marking as read, setting a flag etc.

It must be possible to change only one little data, instead of reindexing the entrie mail (I'm just guessing that that is what happens)

This may not happen on a stronger hardware, but on my netbook this is bad, means it will be a bad idea to run kmail while on battery

Reproducible: Always

Steps to Reproduce:
1. receive mail
2. wait untill the initial indexing of the new mail is done
3. go to an unread mail
Actual Results:  
2-3 seconds of virtuoso-t using > 35% CPU
fan starts

Expected Results:  
mail getting marked as read without such noise

Produced what is in the "Expected Results" box above ;)

One thought is that the file indexing never runs while on battery. Maybe it would be clever to do the same with mail indexing?
Comment 1 Laurent Montel 2015-01-06 20:51:08 UTC
Remove from long time.
=>close it