The way it's currently set up, every time the user interacts with the plot it's entirely redrawn. For a very large resolution, this is prohibitive. The time rescaling is a good way to reduce the resolution, but the code should ideally support high ones.
Whilst switching away from MatPlotLib to Plotly Dash as per #19 would be ideal, in the interim the front-end could be modified to make use of MatPlotLib's 'Blitting' feature that makes it so the graph is only redrawn on demand. This has a bunch of overhead to set up and complicated resizing etc., though.
It would probably be less work than rebooking into Plotly, but Plotly is better in the long run.
The way it's currently set up, every time the user interacts with the plot it's entirely redrawn. For a very large resolution, this is prohibitive. The time rescaling is a good way to reduce the resolution, but the code should ideally support high ones.
Whilst switching away from MatPlotLib to Plotly Dash as per #19 would be ideal, in the interim the front-end could be modified to make use of MatPlotLib's 'Blitting' feature that makes it so the graph is only redrawn on demand. This has a bunch of overhead to set up and complicated resizing etc., though.
It would probably be less work than rebooking into Plotly, but Plotly is better in the long run.