This repository was archived by the owner on Aug 26, 2025. It is now read-only.
fix performance issue with 16k+ sites #36
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Hi!
making some tests I've noticed a huge performance issue using more than 16k sites (2*14+ for precision sake). Making some profiling it results that the splice in clipEdges() slow down a lot with large arrays (from 0.3s for 12k points to 4s for 16k). I've removed de splice, making a new array with unshift and now it take 0.35 for 16k sites and 1.5s for 65k.
hope this fix can be helpful :)
thanks a lot for your work ;)