CPU usage graph uses wrong data
My system is using an Intel i3-4130T CPU, as such it has 2 cores / 4 threads available to it.
The "CPU Usage" graph is showing numbers that make no sense under any scenario that I can come up with.
At the start of this the "Idle" value has an average value of 484. This obviously isn't on a scale of 100% being the maximum... but I can't determine what scale it is using, since if it was using the "each core = 100%" the maximum would still be 400.
The RRD generated graphs in the old UI at least have sensible numbers, even if it doesn't show you the same precision since it's zoomed out to an hour:
#7 Updated by Damian Szidiropulosz over 2 years ago
- Status changed from In Progress to Not Started
- Target version changed from 11.2-BETA1 to 11.3
I've put this back to 11.3 since the entire reports section needs an overhaul. There are reports in there that for design as well as performance reasons need to be rethought. For example some of them don't need to be line graphs at all. Some like disk iops might be better as a summary instead of per disk stat since users with large configurations will not find that useful at all. This ticket was in progress because the work for the new charts was already done with the dashboard overhaul. That dashboard charts work has been completed so there has been some progress made to this end.
#13 Updated by Disk Didler almost 2 years ago
Based on the two example images in this thread, I feel my new job log / incident may have some relevance here.
Certainly feels more consistent and less 'wishy washy' in the old UI. No offense intended, I'm sure it's exceedingly difficult to write decent graphing tools, infact, if I recall, the ones in FreeNAS are using some kind of long term well known graphics generation tool (I don't know the name?)
None the less 'wishy washy' graphs, across the board, are unlikely to impress the hardcore sysadmin types who use FreeNAS, they may frustrate paying TrueNAS customers too.
#19 Updated by Dru Lavigne over 1 year ago
Landon: please refer to the workaround in https://redmine.ixsystems.com/issues/57768#note-16.