Time logging accuracy improvement.

[daved]

The system should be as accurate as possible. For example, the current "500 ms intervals" regularly report somewhere between 500 and 520 milliseconds.

• Is logging to the console adding to the inaccuracy of the gcycle sections?
• Can the order of function calls be arranged to ensure accuracy?
• Can different functions be used underneath?

[abadi199]

I'm not sure if there's anything we can do to improve this. I don't have any experience in this level of application optimization, but I believe since we're relying on RequestAnimationFrame, which means the tick will happen every 16ms (assuming we're getting 60fps). This means, we only have 16ms to finish all the calculation on our update+view function, and according to Firefox performance tools, we're already at 60fps for most of the time here.

And to answer your question:

• Logging to console will definitely affect performance if it was done on each tick, but we're not doing that right now.
• Maybe, but I'm not sure how.
• I'm not sure I understand what you mean by different function. I tried to see if I can use a different data structure in the Game model, but we're currently storing the game logic in a recursive data structure, and I don't think I can replace this without re-writing the whole game engine again.

[daved]

@abadi199 I think you covered everything thoroughly. Thanks for your help!

@nqthqn Please reopen this issue if you see or think of anything that should be addressed.