How do I check CPU utilisation level?
Krzysztof Staniorowski (2787) 57 posts |
While built-in “Tasks” feature offers detailed view into memory utilisation stats there’s basically nothing about how hard CPU works. After short research I wasn’t able to find an app offering CPU stats (current MHz, utilisation percentage, preferably also which app causes load) – is there any? |
David Pitt (102) 743 posts |
|
Krzysztof Staniorowski (2787) 57 posts |
Thank you so much :-) exactly what I was looking for. |
Mike Freestone (2564) 131 posts |
So short that !Usage in the Utilities directory didn’t turn up! It also does what you’re asking minus the megahertz report |
David Pitt (102) 743 posts |
And |
Chris Hall (132) 3554 posts |
There’s also !CPUClock and !CPUFreq available from !Store to display clock speed on the OMAP3, OMAP4 and ARMX6 platforms. |
rob andrews (112) 200 posts |
Don’t forget OMAP5 too |
Krzysztof Staniorowski (2787) 57 posts |
Mea culpa, I should look anywhere outside Apps dir before trying to google something to buy/download.
Is it compatible with Raspberry Pi B+ then? As far as I know it’s “armv6l”. OT: is it normal that !NetRadio (with its !MPlayer) consumes 50-65% of CPU (o/c to 800MHz) just playing 128kbit/s BBC R4 stream? |
David Feugey (2125) 2709 posts |
It does not really consume. It has. Don’t forget it’s cooperative multitasking. |
Chris Gransden (337) 1207 posts |
The version here should get cpu usage down to about 10%. |
Krzysztof Staniorowski (2787) 57 posts |
I wasn’t able to make it run because it needs SharedUnixLibrary 1.13 (and version from here isn’t the latest afaics). |
David Pitt (102) 743 posts |
|
Krzysztof Staniorowski (2787) 57 posts |
thank you :-) |
David Feugey (2125) 2709 posts |
Latest build is here : Should be the same… |
Krzysztof Staniorowski (2787) 57 posts |
Well, this newer !MPlayer is much less stable (keeps throwing “Audio device got stuck!” error in some cases when I’m changing station in !NetRadio). Still, only 10-15% of CPU usage :-)
thanks again |
David Pitt (102) 743 posts |
Not quite! The latest build #37 actually contains SharedUnixLibrary 1.14. There appears to be one fix of a memory leak from 1.13. The latest build of both gcc 4.7 and SharedUnixLibrary can be found from these URLs :- http://ci.riscos.info/job/gcc-4.7-native http://ci.riscos.info/job/gcc-4.7-native/lastSuccessfulBuild/artifact/ |