https://bugs.kde.org/show_bug.cgi?id=305966
Bug ID: 305966 Severity: normal Version: 4.9.0 Priority: NOR Assignee: kdepim-bugs@kde.org Summary: changing message state leads to 2-3sec 40% CPU abuse by virtuoso-t Classification: Unclassified OS: Linux Reporter: and...@alweb.dk Hardware: Other Status: NEW Component: misc Product: kmail2 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? -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs