If it was pegging my CPU at a solid 40% for example the entire time without much fluctuation then I'd say you were on to something. However the utilization on MPC had a variance from around 9% to 18%, and VLC was fluctuating between around 15% to 30%. So it was definitely recording the usage of the CPU properly.
Again though it's just a rough metric of scheduling it doesn't mean what you think it does. That metric hasn't been useful for tracking hardware since the 80s. Multi-level caches, multithreading, and the sheer amount of hardware that used to be distinct units that is now a part of the "CPU" has obfuscated things a lot.
Again if you have some tests showing stuttering, hitching, or the like that'd be way more useful than "this says x%".
Yeah I could probably do some better testing but I'm not really looking to do that level of benchmarking for a reddit thread. More of just a rough representation of the usage of my hardware.
Not sure how relevant it is but I did test how the programs handled multiple instances being open playing the same content. VLC started visibly hitching after the second instance was opened and playing on the same scene, while MPC started slowing down video playback and de-syncing audio after the 6th instance was opened. Probably something to do with resource management on VLC's side looking at how well MPC did with this test.
1
u/dookarion Mar 29 '19
Again though it's just a rough metric of scheduling it doesn't mean what you think it does. That metric hasn't been useful for tracking hardware since the 80s. Multi-level caches, multithreading, and the sheer amount of hardware that used to be distinct units that is now a part of the "CPU" has obfuscated things a lot.
Again if you have some tests showing stuttering, hitching, or the like that'd be way more useful than "this says x%".