-
-
Notifications
You must be signed in to change notification settings - Fork 8.3k
PERF: Sticky edges speedup #31244
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
Merged
+54
−26
Merged
PERF: Sticky edges speedup #31244
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
5bbd7a1
Speed up sticky edges handling
scottshambaugh 874fe77
Lazily construct sticky edges
scottshambaugh f188cd8
Skip most children for sticky edge checks
scottshambaugh cb3f9fd
Skip sticky searching if empty
scottshambaugh ac439c8
Code review updates
scottshambaugh File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Slighty worried that this is unnecessary micro-optimization.
Do 20ns per artist really make a difference? If not, I'd rather stay within the public API bundaries
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does show up in the results - just the
.sticky_edgesproperty accesses are the circled bits in the baseline profiling here. Becauseautoscale_viewis called for each scatter call in the script, this inner loop is O(n^2) with the number of artists. We could defer autoscaling or be smarter about which artists are on the boundary, but that would be a much bigger change.