CPU utilization too high about javidx9

[OneLoneCoder]

Hey, Typically "throttling" would be down to the user - there are several ways to achieve it, the simplest being just calling "this_thread::sleep_for(20ms)" would lock it to 50fps - however, that also locks up user input and everything else.

[gurkanctn]

I had guessed that throttling could be an option in CGE. Thanks for the response.

I think I'll work on throttling, once I can set up Netbeans to compile the header.

Should I close this issue, or keep it open for further discussions on throttling?

[OneLoneCoder]

By all means keep it open, its an interesting topic in its own right!

…

On Tue, Jul 31, 2018 at 7:36 PM My Name ***@***.***> wrote: I had guessed that throttling could be an option in CGE. Thanks for the response. I think I'll work on throttling, once I can set up Netbeans to compile the header. Should I close this issue, or keep it open for further discussions on throttling? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#16 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AYPeevBDfMZB2Gmi2HFhh5cvtx5RCRd3ks5uMKOjgaJpZM4VXAud> .

[michaelshmitty]

Just chiming in here with an observation: I often keep an eye on the CPU usage graph in Visual Studio debug mode in @OneLoneCoder 's videos when he runs the code and I never really see it spike or run the CPU really hot.

@OneLoneCoder brilliant channel, thanks for the great videos and insight.

[giampierosalvi]

Hi,
I have used the SDL_Delay function to slow down the updates and it worked very well (for example delaying by 10 or 20 milliseconds as suggested by @OneLoneCoder ). Something that I did not manage to achieve is to decide on a constant update period (say 0.02 sec) and use the (0.02-fElapsedTime) * 1000 as an argument to SDL_Delay. Somehow this does not work. I suspect there could be a problem with the granularity of those delay functions that are usually around 10 or 20 ms.

I also want to mention, that this issue can go beyond the CPU getting hot. On one desktop with 8 i7 cores, the examples run fine, although they take ~100% of one of the cores and have a FPS of 1800. However, on an intel nuc, with 4 i5 cores, the examples lock the computer's graphical interface completely (at around 5-600 FPS). I have been running the SDL version on Ubuntu 18.04, but I suspect this could happen on not that powerful windows machines as well. The only way to kill the process was to enter a text based login because the graphical interface was completely unresponsive.

Great job by the way.