Bug #7037
closedCPU frequency in System Information
0%
Description
On dashboard under "CPU Type" the "Current" frequency rarely appears. Maybe 1 in 10 refreshes? This is with refresh interval set to 5 seconds. The appearances seem random.
On 2.3.1 I can't say I noticed this stat at all. Might have been up to config. I now noticed because when it appears/disappears the column changes height.
Files
Updated by Kill Bill almost 8 years ago
This only shows when the actual CPU freq is lower than max. By taxing the CPU with reloading the dashboard every 5 seconds, you probably won't ever see it.
Updated by Aslak Sande almost 8 years ago
That seems reasonable, but resizing the column on refresh is not pretty. I don't see any reason to why it should't show the frequency regardless of max frequency or not.
Updated by Jim Pingle almost 8 years ago
- Status changed from New to Not a Bug
If the frequency is at maximum, the information is redundant and thus hidden. There isn't any reason to think it isn't running at full speed unless another frequency is shown.
Updated by Aslak Sande almost 8 years ago
The info might well be redundant, but dynamic resizing from different values is poor design.
Updated by Steve Russell almost 5 years ago
Is there any chance of reconsidering this? The problem is the whole rest of the column continually jumping up and down because of an optimization that serves no obvious purpose.
Thanks.
Updated by Jon8RFC . over 2 years ago
Is there a quick and dirty way to manually force this to always display?
It's just one line and I would rather it stay put than come and go.
I'm also curious to see in the UI if/when an Intel core goes into turboboost. If that capability exists and is just being hidden by a "hide if >= default speed" setting, It'd be nice if that's not the default behavior.
I had been concerned, thinking there was an occasional problem with not being able to poll my cpu on this brand new box. I didn't use powerd on my old one. It's relieving to find this in redmine.
Thanks for all your work on these seemingly little, yet big, things (like the upnp issue!) for us, Jim.