| Summary: | Amarok spectrum analyser high CPU usage when idle | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Jan Stolarek <jwstolarek> |
| Component: | tdemultimedia | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | NEW --- | ||
| Severity: | normal | CC: | bugwatch, jwstolarek, michele.calgaro, slavek.banko |
| Priority: | P5 | ||
| Version: | R14.0.x [Trinity] | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
| Attachments: | Idle animation on the default spectrum analyser | ||
Hi Janek, question: which Amarook engine are you using? In case it is xine, which version of xine and TDE? I'm using libxine2 1.2.9-1: https://packages.debian.org/buster/libxine2 and TDE 14.0.9 PSB. ok, thanks Janek. Would you be able to test Amarok R14.0.8 for comparison? There has been a recent change in the Amarok scope plugin, so it would help to see if that is the cause of the high cpu you see. Also, would you be able to test on a different computer? I don't see any particular CPU usage here > Would you be able to test Amarok R14.0.8 for comparison? I tried but I'm not sure if I downgraded correctly. I installed 14.0.8 versions of amarok-trinity, amarok-common-trinity and amarok-engine-xine-trinity fro the 14.0.8 repository, bu the version reported by `amarok --version` is the same as for the PSB repository. If that was a correct downgrade then the results are the same - still around ~5% COU usage on idle. > Also, would you be able to test on a different computer? I tested on a laptop that also runs TDE PSB and I get the exact same results. > I tried but I'm not sure if I downgraded correctly.
Uhm, it should say R14.0.8, PSB says R14.0.9 [DEVELOPMENT].
PSB already contains the latest changes, that is why I asked to test on R14.0.8.
Maybe Amarok was still running from before in the sys tray?
Hmm... nNot sure what I did wrong. `amarok --version` says: Qt: 3.5.0 TDE: R14.0.9 [DEVELOPMENT] Amarok: 1.4.10 And to be clear: I downgraded Amarok *only*, not TDE itself. I also logged out and in again to make sure Amarok is not running in the background. I also cleaned Amarok configuration to make sure there are no leftovers from my normal config. I can confirm the above problem - Amarok on Wheezy (Xine 1.2.2). Hi Slavek, when you have time could you try rebuilding amarok without commit c5f901c03ec and see if the problem still happens in Wheezy? This will help understanding if the problem was preexisting or not. In bullseye I can't test that since I have xine 1.2.10 and without that commit ther would be a FTBFS. Thank you! Slavek was able to test Amarok R14.0.8 on Wheezy and the problem is still happening, so it is not related to the commit to fix xine 1.2.10 support but instead caused by something else. I just realized that the default analyser (only) has a refresh rate setting available under right click. Setting lower FPS reduces the CPU usage, which can be a workaround for someone who doesn't want to completely disable the analyser. |
Created attachment 2984 [details] Idle animation on the default spectrum analyser On a 3,8GHz CPU Amarok uses the following percentages of CPU time: <0,7% when idle and minimized (either to system tray or to the taskbar) ~2% when playing mp3 and minimized ~5% when idle and not minimized ~6% when playing mp3 and not minimized (the numbers don't add up, I know) After tedious debugging it turns out that this is because of the spectrum analyser, and the CPU usage when idle is caused by idle animation on the analyser (see attached screenshot). While I understand that the analyser has to use some CPU time when used during playback I don't think it's justified to use as much CPU when nothing is being played. In fact, the second analyser uses as much as 10% CPU time in idle state. To put these percentages into perspective: Xorg server uses around 1-5% when drawing TDE windows, while idle Firefox with 10-15 tabs uses ~7% CPU time. As a workaround it's possible to not select any analyser (downside: annoying text telling you to click to pick a spectrum analyser) or remove the analyser from the bar altogether via toolbar configuration (subjective downside: weird toolbar layout). Aside: 5% of 3,8GHz is 190MHz. When I first used KDE3 over 15 years ago I had a 500MHz Pentium III and IIRC that analyser was already there. No way it used over a third of my CPU speed back then.