Has anyone else noticed this / does anyone care / have any suggestions? My thoughts are that Chrome should be capable of simply demanding more CPU access when running a demanding game, so games like mine can run all of their data processing unimpeded. Perhaps a game maker could raise a flag to permit this to happen. Am I being naive - is Chrome's access to processor time controlled by Windows or can it demand more if it needs it.
You have to be very careful how you test you game when it comes to CPU and FPS and what conclusions you draw from them.
Using the debugger to validate CPU and FPS are extremely unreliable and depending on how you measure it you get different results, that you cant really use to a lot I think.
Here is an example:
All tests are made from the same place in the game.
1. The first image shows the stats that I get using the Debugger in NW.js when the system tab is selected.
2. Second image show how much this information changes simply by changing tab from system to a another tab.
3. Is without debugger tracking the data in game and fits well with the second test when using debugger.
So when testing performance you have to take into account which tab you have selected in the debugger. And at least in my opinion, doing any testing in the system tab is completely useless, because you cant use of any of the data you get there to anything, it doesn't reflect your game performance, but the game and the debugger performance combined.