Ah very cool. I thought this was going to be a tongue-in-cheek article about the proliferation of random corporate-mandated CPU hogs like croudstrike or w/e.
Pleasantly surprised by the technical article :). Reminds me of a lot of precise-number-of-idle-cycles functions from embedded world in a prior life
Likewise. Wasting user space CPU cycles is actually a moderately tricky thing to do when we have optimising compilers. Its not something that comes up a lot but it is occasionally something you do need to do in order to test other things and it is different to making a lot of system calls.
I think volatile is usually fairly well contained I can't immediately think of an obvious case where it could adjust the performance of the calling context indirectly but its pushing the problem onto that cache coherence part of the CPU so its not quite the same as an algorithm that consumes all the memory bandwidth or execution ports. Lots of little interesting trade offs in the weeds of this and other potential solutions depending on if any of this matters.
Fair enough, also thinking about it some more. If you use that option the old 90% will usually be normalized to 100% so this might not even be helpful.
it's funny because you can buy old flagships on ebay and the battery craps out
but the replacement battery you buy is counterfeit like Lenovo Carbon for example
Ah very cool. I thought this was going to be a tongue-in-cheek article about the proliferation of random corporate-mandated CPU hogs like croudstrike or w/e.
Pleasantly surprised by the technical article :). Reminds me of a lot of precise-number-of-idle-cycles functions from embedded world in a prior life
Likewise. Wasting user space CPU cycles is actually a moderately tricky thing to do when we have optimising compilers. Its not something that comes up a lot but it is occasionally something you do need to do in order to test other things and it is different to making a lot of system calls.
I think volatile is usually fairly well contained I can't immediately think of an obvious case where it could adjust the performance of the calling context indirectly but its pushing the problem onto that cache coherence part of the CPU so its not quite the same as an algorithm that consumes all the memory bandwidth or execution ports. Lots of little interesting trade offs in the weeds of this and other potential solutions depending on if any of this matters.
The "stress" command is pretty good for this.
These days it's all about wasting GPU like a professional
Stop gatekeeping. With vibe coding anyone can waste GPU.
I have this compulsion to not close my laptop if the battery is over 90% so I would open up html5 fishbowl and crank it up to 50,000 fish per window.
I was looking for some script like count primes I could run
Why not instead limit the charging level to 90%? Should save battery life as well.
depends on the laptop if it has that setting or OS
Fair enough, also thinking about it some more. If you use that option the old 90% will usually be normalized to 100% so this might not even be helpful.
it's funny because you can buy old flagships on ebay and the battery craps out but the replacement battery you buy is counterfeit like Lenovo Carbon for example
It's easy, just use Windows
Would it use less power on ARM architecture?