Bug 305966

Summary: changing message state leads to 2-3sec 40% CPU abuse by virtuoso-t
Product: [Applications] kmail2 Reporter: Anders Lund <anderslund>
Component: miscAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED INTENTIONAL    
Severity: normal CC: montel
Priority: NOR    
Version: 4.9.0   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

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