Currently we serialize and send the entire game state to the editor every singe frame. This potentially puts an unnecessary load on the editor, which has to process and re-render the entire game state 60 times per second. In practice we only need to update the editor maybe 5-10 times per second in order to avoid any visual lag for the end user. As such, reducing the rate at which we send the data to the editor could potentially fix some performance issues, specifically randomPoison/amethyst-editor#26.
Note that while most of the game data should only be sent infrequently, we still need to send log data every frame.
Currently we serialize and send the entire game state to the editor every singe frame. This potentially puts an unnecessary load on the editor, which has to process and re-render the entire game state 60 times per second. In practice we only need to update the editor maybe 5-10 times per second in order to avoid any visual lag for the end user. As such, reducing the rate at which we send the data to the editor could potentially fix some performance issues, specifically randomPoison/amethyst-editor#26.
Note that while most of the game data should only be sent infrequently, we still need to send log data every frame.