You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It should be easy to add a performance metrics tracker for debugging purposes.
Things that should be tracked:
Duration of message processing step
Duration of Pipeline::prepare_render
Duration of Pipeline::render
Duration of client code frame generation
Frame-to-frame elapsed time
These metrics don't necessarily need a big object, they can be stored in a struct of floats and updated via exponentially-weighted moving average with a low coefficient like 0.1 which should stabilize after 100 frames.
The text was updated successfully, but these errors were encountered:
It should be easy to add a performance metrics tracker for debugging purposes.
Things that should be tracked:
Pipeline::prepare_render
Pipeline::render
These metrics don't necessarily need a big object, they can be stored in a struct of floats and updated via exponentially-weighted moving average with a low coefficient like 0.1 which should stabilize after 100 frames.
The text was updated successfully, but these errors were encountered: