-
Notifications
You must be signed in to change notification settings - Fork 6
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
Performance audit #111
Labels
Comments
DanielVandH
added
documentation
Improvements or additions to documentation
enhancement
New feature or request
help wanted
Extra attention is needed
and removed
enhancement
New feature or request
labels
Jul 6, 2024
I'm going to close this for now. I have some plans to improve performance in some areas, including a refactoring of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Now that the package is a stable state, it would be a good idea to do a performance audit and track the performance of the package over each version. This could also be run in the CI, although I'm not sure how to set that up and I'm not particularly bothered one way or about this. This tracking could be at a high level to start with, and then as problematic functions are identified I could add tests of those lower-level functions into the test suite. Some good benchmarks to track would be:
find_polygon
)statistics
of a triangulationThe text was updated successfully, but these errors were encountered: