xps13 | : neckbeard : DELL xps13 2015 Linux Support

I am using Matplotlib widget slider on a figure having many plots. When I move the slider it takes about 5 s to update the figure and that is my problem.

After troubleshooting the problem, it seems that the culprit is the widget itself that calls fig.canvas.draw(). When not doing any action (not modifying any of the subplots) on moving the slider it is still taking 5s to update the slider because fig.canvas.draw() makes it replot all the figure with all the subplots each time I touch the slider.

In all threads complaining about Matplotlib plotting speed, like here: why is plotting with Matplotlib so slow?, it is advised to not use fig.canvas.draw() because it redraws the whole figure but use ax.draw_artist() instead to only replot the data of the subplot that has been modified. So Matplotlib widget is ruining all my efforts to make this plot interactive (5s lag is not really interactive). I would have known before I would probably have gone with a different library, but it is too late now.

This problem was actually brought up in 2013 (http://matplotlib.1069221.n5.nabble.com/Making-an-interactive-plot-faster-td41312.html) and it was suggested to have the option to use draw_artist instead. The possibility to set drawon to False doesn't work for me because, as explained in this post, the widget calls fig.canvas.draw() at least once anyways. Since this problem was first brought up, almost 8 years ago, has there been any improvement (that I haven't found) to make Matplotlib widget only update the widget and let the user decide what element on the figure should be updated as well?

I think that it is a major limitation of Matplotlib widgets and I really hope there is a way to correct this behaviour. In my case I could probably speed up the plot by plotting the biggest plot (which is static) as an image or reduce the number of points, but it will still be less efficient than just having widgets not redraw it everytime.

--------------------UPDATE----------------------

After creating the figure and only adding the widgets (5 sliders, 4 buttons, 1 radio button) and 3 empty subplots, the sliders already lag! At this point there is no data, only 10 widgets and 3 empty subplots on a figure, and there is already about 0.5s - 1s lag (by eye) everytime I want to move a slider. If I move a slider continuously up and down my CPU jumps from 15% to 50%! I have a Dell XPS13 with i7 7660U (2 cores 4 threads with 4GHz turbo). I don't understand how moving 1 slider can be so CPU intensive. What is so heavy for matplotlib to calculate? As a result, I don't have any workaround anymore. My idea of replacing the biggest plot by an image is not very useful since even without any data or image the slider is already too slow!

Does anyone understand how moving 1 slider can be so crazily cpu intensive, and most importantly, how to avoid this lag each time I touch a slider?

Thanks

Here is an example of the code I use to generate the figure with 10 widgets and 3 empty subplots.

I run Arch Linux with I3 on an XPS13 with 3200x1800 res screen.

I'm currently working on some Swing apps. When I run my app from the commandline with the java -Dsun.java2d.uiScale=2 myApp, the app is scaled (else it's just too small).

I also have the same line in my vmoptions file, but for some reason IntelliJ Idea does not upscale my Swing app when I run it.

How can I get IntelliJ idea to scale my Swing app?