Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Optimizations #23

Open
skygering opened this issue Oct 26, 2023 · 2 comments
Open

Optimizations #23

skygering opened this issue Oct 26, 2023 · 2 comments

Comments

@skygering
Copy link
Collaborator

Functions that could be parallelized (please add as we go so that we can optimize later):

  • Signed area could conceivably be multithreaded
@rafaqz
Copy link
Member

rafaqz commented Oct 26, 2023 •
edited
Loading

Probably parallelising apply at the level of Vectors, FeatureCollections or MultiPolygons would be effective. We could have a threaded keyword and make it false after we thread at the outer level.

I can PR with this at some point.

@rafaqz rafaqz mentioned this issue Oct 26, 2023
Merged
@asinghvi17
Copy link
Member

https://www.crunchydata.com/blog/performance-improvements-in-geos may be a useful way to compare ourselves against LibGEOS (for at least some of the benchmarks)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rafaqz @asinghvi17 @skygering