One peculiar consequence of fat CPUs with enormous core counts is that measuring CPU load in percentage of allocated time slots - as in, most monitoring software does now - is kind of useless.

For example, when talking about a CPU with 64 logical cores, one process utilising two cores to the full will only show up as 3% load, and yet this might just be enough to ramp up the cooling system and make some noise. Meanwhile, a bunch of small loads spread across the cores will add up to the same 3% and yet the overall load will be lower, your fans will stay quiet. If you throw dynamic clocking into the mix, the entire idea of counting allocated time slots goes to shit. 50% load on a core at 2GHz and 50% load on a core at 5GHz are entirely different things. Therefore, this metric is most useless any way you look at it.

The better idea, as I see it today, would be to RETVRN to tradition and measure load in... Watts against the maximum TDP that your CPU can draw. A mostly idling CPU at low clock wouldn't draw much power, whereas a CPU at high load would draw as much as possible. Number of processes or cores loaded doesn't matter here, and the number is pretty easy to grasp.

Follow

@icon_of_computational_sin
Game os running at 15fps.
I check CPU: 10 %. GPU: 5% Ram: 10GB free...

It's so fucking tiresome. JUST TELL ME WHAT TO UPGRADE FFS!!!

Sign in to participate in the conversation
Game Liberty Mastodon

Mainly gaming/nerd instance for people who value free speech. Everyone is welcome.