-
Notifications
You must be signed in to change notification settings - Fork 154
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
Adds pairwise_point_polygon_distance
benchmark
#1131
Merged
rapids-bot
merged 80 commits into
rapidsai:branch-23.06
from
isVoid:benchmark/point_polygon_distance
May 23, 2023
Merged
Adds pairwise_point_polygon_distance
benchmark
#1131
rapids-bot
merged 80 commits into
rapidsai:branch-23.06
from
isVoid:benchmark/point_polygon_distance
May 23, 2023
Conversation
This file contains 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
…into feature/polygon_distances
…into feature/polygon_distances
…oid/cuspatial into benchmark/point_polygon_distance_dev
…into benchmark/point_polygon_distance_dev
…into benchmark/point_polygon_distance_dev
…into benchmark/point_polygon_distance_dev
…into benchmark/point_polygon_distance_dev
github-actions
bot
added
cmake
Related to CMake code or build configuration
libcuspatial
Relates to the cuSpatial C++ library
labels
May 9, 2023
isVoid
added
feature request
New feature or request
non-breaking
Non-breaking change
labels
May 9, 2023
harrism
approved these changes
May 10, 2023
/merge |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
cmake
Related to CMake code or build configuration
feature request
New feature or request
libcuspatial
Relates to the cuSpatial C++ library
non-breaking
Non-breaking change
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.
Description
This PR separates the
pairwise_point_polygon_distance
benchmark portion of PR #1002. While that PR is only left for nvtx3 experiments.Original PR description:
This PR adds pairwise point polygon distance benchmark. Depends on #998
Point-polygon distance performance can be affected by many factors, because the geometry is complex in nature. I benchmarked these questions:
How does the algorithm scales with simple multipolygons?
The benchmark uses the most simple multipolygon, 3 sides per polygon, 0 hole and 1 polygon per multipolygon.
Float32
Float64
The chart shows that with simple polygons and simple multipoint (1 point per multipoint), the algorithm scales pretty nicely. Throughput is maxed out at near 1M pairs.
How does the algorithm scales with complex multipolygons?
The benchmark uses a complex multipolygon, 100 edges per ring, 10 holes per polygon and 3 polygons per multipolygon.
float32
float64
The algorithm reaches max throughput at near 10K pairs. About 100X lower than the simple multipolygon example.
Checklist