[1.1.3.9] I strongly disagree with the new CPU usage policy
Posted: Fri May 05, 2023 4:00 pm
Ever since it was introduced, I check new patches to see if it's "fixed"
I'm talking about that performance change that makes the cpu go 50% usage when paused with a freshly started galaxy.
I'm against the idea and here is why. I like to play games in the background. Do some work, alt tab give some orders, alt tab work etc. Now, if I leave system load target at the default 60, my cpu is 50% usage all the time. It does not matter I'm in game, or if I'm paused or if the game is minimized. It's 50% usage ALL the time. If I reduce it to minimum it goes to 25%. This still enough for my laptop coolers to take off and just spin spin spin.
We live in a modern world. C# is a high level language. It has so many ways of synchronizing threads, and signaling and locking. Must we really do while(true) or thread.sleep on all workers or whatever it is happening?
Can we not execute work when work is available to be executed?
I hope this way of doing this is just for the beta, but I keep checking the logs and it seems it's not being touched anymore.
for reference I'm on a laptop with Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
I'm talking about that performance change that makes the cpu go 50% usage when paused with a freshly started galaxy.
I'm against the idea and here is why. I like to play games in the background. Do some work, alt tab give some orders, alt tab work etc. Now, if I leave system load target at the default 60, my cpu is 50% usage all the time. It does not matter I'm in game, or if I'm paused or if the game is minimized. It's 50% usage ALL the time. If I reduce it to minimum it goes to 25%. This still enough for my laptop coolers to take off and just spin spin spin.
We live in a modern world. C# is a high level language. It has so many ways of synchronizing threads, and signaling and locking. Must we really do while(true) or thread.sleep on all workers or whatever it is happening?
Can we not execute work when work is available to be executed?
I hope this way of doing this is just for the beta, but I keep checking the logs and it seems it's not being touched anymore.
for reference I'm on a laptop with Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz