Add hillshade benchmarking for numpy, cupy and rtxpy #625
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds a benchmark for
hillshadefornumpyarrays (calculated on CPU) andcupyarrays (calculated on GPU). Also thertxpyversion of hillshade that calculates full shadows, so the timings of this are not directly comparable with the two other implementations as it is performing many more calculations.Timings on my dev machine (Quadro T1000 graphics card) show that GPU algorithm is ~1.5 orders of magnitude faster than CPU algorithm for rasters of dimension ~1000 and over 2 orders of magnitude faster for dimension ~3000.