Improve draw performance - #781
Draft
cvanelteren wants to merge 6 commits into
Draft
Conversation
cvanelteren
force-pushed
the
interactive-draw-performance
branch
from
July 29, 2026 20:54
c2d87d1 to
18d4e4b
Compare
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces several improvements in drawing graphs. It achieves this by optimizing the draw request. Currently, when a draw requests comes in, the entire graph is redrawn, which can be inefficient. The new approach allows for more targeted updates, reducing unnecessary redraws and improving performance.
How it works When a draw requests comes in, we cache the layout to see if a layout needs to be adjusted (otherwise it is drawn immediately). If the layout did change, we reuse tick calculations and axes measurements, then we re-use cached layouts where possible to improve performance further.
The end results it that we can improve draw performance, especially versus tight layout in raw matplotlib.
EDIT: just wanted to emphasize that we are not optimizing how data is handled. So when the data increases the two performances will align. What we do here, is optimize the surrounding infrastructure to prevent unnecessary redraws when there is no change. I am trying to figure out if we can do the other stuff too but in a different PR.