Bug 312919 - high CPU usage for copying notification
Summary: high CPU usage for copying notification
Status: RESOLVED UNMAINTAINED
Alias: None
Product: plasma4
Classification: Unmaintained
Component: notifications (show other bugs)
Version: 4.9.97 RC2
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-09 00:14 UTC by Martin Bednar
Modified: 2018-06-08 18:25 UTC (History)
21 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Bednar 2013-01-09 00:14:36 UTC
When downloading a file with kget and desktop notification enabled, I noticed a higher CPU usage by plasma-desktop. I checked this with regular copying (sftp, disk to disk), and it happens every time. 


Reproducible: Always

Steps to Reproduce:
1.add notification widget
2.copy file large enough to have time for other actions
3.see plasma-desktop consume CPU
Actual Results:  
above average CPU usage.


When copying a file through sftp, the sftp ioslave takes 16% of CPU, plasma-desktop takes as much. (this is on a Core2Duo 1.2 gHz laptop). Removing the notifications gets me rid of this plasma cpu usage. (I am not talking about the mode where it draws the graph, but about when everything is collapsed and all I see is the spinner)
I performed a couple more very unscientific tests : 
Core2Duo 1.2gHz : 16% Cpu usage (the aforementioned machine)
Core2Duo 3.0 gHz : 6% CPU usage
Atom 270           :  30% CPU usage! (that's a lot for a simple spinner).

Granted a simple workaround is to simply disable file transfer notifications in the widget.
Comment 1 Martin Bednar 2013-01-09 00:48:15 UTC
Jus found out that to trigger this, the following bug can be used : https://bugs.kde.org/show_bug.cgi?id=312920
Comment 2 Kai Uwe Broulik 2013-01-09 10:46:11 UTC
Duplicate of https://bugs.kde.org/show_bug.cgi?id=311799 ?
Comment 3 Martin Bednar 2013-01-09 12:13:53 UTC
Not sure, here Xorg usage stays normal, only plasma-desktop shows higher CPU usage, and never 100%. Very possibly related though. I wouldn't mark it as duplicate, but as closely related, ie when one is fixed, check the other.
Comment 4 Kai Uwe Broulik 2015-01-01 20:35:20 UTC
Can you verify with recentmost plasma-framework checkout? CPU consumption seems only slightly elevated (8-11%) now that the popup is actually aware that it's not rendering.
Comment 5 Eugene Shalygin 2015-01-07 20:48:46 UTC
Not exactly the same problem, but may be related. With Plasma 5 from  Git master and Kopete 14.12, when Kopete receives a message and attracts my attention by changing its icon, plasmashell uses 20-40% of one core of Core i7-4810MQ, which is enough to make it loud in my setup after some time.
Comment 6 Eugene Shalygin 2015-01-13 23:06:52 UTC
When plasma-nm asks for a credential during connection (icon shows spinnig cirle), plasmashell takes 140% of CPU, Xorg uses roughly 50%. Core i7-4810MQ. 

Guys, this is simpy disgusting. It seems like just each tray animation behave in such brutal way. I remember there were a lot of talks how nicely Qt Quick based plasma renders, how fast it is, how *optimized* it is :). And now what? To show a shiny spinnig circle a half of quad-core CPU is needed?
Comment 7 Manuel Bärenz 2015-11-27 15:21:48 UTC
This still persists in Plasma 5.
Comment 8 AnAkkk 2015-12-25 19:38:06 UTC
Seems like this is the same as:
https://bugs.kde.org/show_bug.cgi?id=356479
https://bugs.kde.org/show_bug.cgi?id=357099
Comment 9 Marco Leise 2016-06-24 15:11:44 UTC
I once copied a 2 GiB hiking map to a USB 1 GPS device from my notebook while on battery in a car and I bit my lips that I used Dolphin and not "cp". The tray icon seemed to say: "Do you want to play a little game? Guess what is done earlier, the file transfer or your battery." It finished in time, but it would be nice if these animations used a little less power than e.g. watching a HD H.264 video (6-7W). :D
Comment 10 Bart 2017-01-11 21:36:48 UTC
As someone pointed out, this persists in Plasma 5.8. In 2017. Copying a file, generating a GPG key or connecting to a wifi network destroys battery life.
Comment 11 Christoph Feck 2017-01-19 14:49:26 UTC
Please read bug 348764 comment #4.
Comment 12 Dreyk 2017-03-26 23:10:51 UTC
Moved from https://bugs.kde.org/show_bug.cgi?id=356479#c122

KDE 5.9.4 and all previous.

Plasma uses 100% CPU (Intel Core i7-2670QM) load, when there is an any animation in the task bar or system tray.

This cause only when i switch to Nvidia Prime card (notebook with Nvidia Optimus). When I switch back to Intel integrated graphics - everything is fine. So several years already I can not use Nvidia card with KDE desktop :(
Comment 13 TOM Harrison 2017-03-27 13:01:26 UTC
my experience is reverse. my plasmashell is using almost 100% if i using intel graphical card.
Comment 14 Dreyk 2017-03-27 20:45:01 UTC
I must to clarify that, when I use Nvidia card and got high CPU load, animations in system tray bar rotate with a crazy high speed (I think this is the main reason).

(In reply to Dreyk from comment #12)
> Moved from https://bugs.kde.org/show_bug.cgi?id=356479#c122
> 
> KDE 5.9.4 and all previous.
> 
> Plasma uses 100% CPU (Intel Core i7-2670QM) load, when there is an any
> animation in the task bar or system tray.
> 
> This cause only when i switch to Nvidia Prime card (notebook with Nvidia
> Optimus). When I switch back to Intel integrated graphics - everything is
> fine. So several years already I can not use Nvidia card with KDE desktop :(
Comment 15 Christoph Feck 2017-04-21 14:23:28 UTC
Please do not add comments to 'plasma4' tickets if you are using Plasma 5.
Comment 16 Nate Graham 2018-06-08 18:25:52 UTC
Hello!

This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug has already been resolved in Plasma 5.

Accordingly, we hope you understand why we must close this bug report. If the issue described  here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting

If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging

Thanks for your understanding!

Nate Graham