-
Notifications
You must be signed in to change notification settings - Fork 294
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Python interactive window drops fps when creating many plots - SVG rendering is slow #3279
Comments
after latest update I have same problem. please fix it! |
Rendering to png instead of svg might speed this up. Try adding this cell first:
|
Note, that change eliminates the ability to expand the plots later. |
I'd really like to keep the ability to zoom into plots. Not sure if this was already considered but if the number of rendered elements are a problem, I believe |
Possible solution - Generate PNGs along with the SVG, but only display the PNG in the history window. When the plot viewer opens, use the SVG. |
@rchiodo thanks! It works! |
@DavidKutu my fix for #3233 should fix this too. |
@rchiodo isn't virtualizing an option? |
@DonJayamanne yes we want to do that too. Something like this looks promising: However, SVG is a lot slower than PNG. We can fix jupyter to generate both. |
How do I do that? |
@ParteekSJ Nothing you have to do. This is something the Jupyter extension now does internally. |
Thank you. |
Not sure how hard it is to do anything about this but I noticed that if the Python interactive window contains lots of plots already (above maybe 30), adding new ones brings the frame rate down quite significantly. Above around 60 plots, it's at less than 1 fps and makes all of VS Code become unresponsive. Once the plots are done, VS Code (including the interactive window) returns to normal.
Here's some example code to reproduce the issue.
The text was updated successfully, but these errors were encountered: