Quickly modifying a plan multiple times in quick succession bogs the UI as it re-renders

[duranb]

It was found that if someone is programmatically modifying a plan that someone else is viewing the UI of, those quick db mutations trigger the UI to re-render after every update. This causes a decrease in responsiveness in the UI.

We should look in to debouncing the re-render of the timeline or something to that effect.

[duranb]

Finding from @sqlAlchemyNoob2004:

Plans page susceptible to client side latency spikes if there is a lot of websocket traffic. While the server appears to handle high load, an individual client struggles to keep up if there is a high volume of data being received over the websocket connections. Data (especially plan updates) causes the center chart to re-render repeatedly and frame rate plummets. Could consider batching updates that would cause the chart to re-render or look into tuning the rendering itself.