⚗️ Benchmark nvTIFF CUDA GPU-based decoding #4
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.
Benchmark reading the LZW-compressed GeoTIFF to CUDA GPU memory via DLPack. Using
cog3pio's CudaCogReader which uses bindings to thenvTIFFlibrary.Steps
cargo bench --features cudaResults
Ran on my laptop with a NVIDIA RTX A2000 8GB Laptop GPU. CPU benchmarks ran on 12th Gen Intel® Core™ i5-12600HX with 16 threads. Note that CPU benches include host to device memory copy too, so should be slightly slower than #3.
nvTIFF is nice and fast. LiberTIFF is holding up nicely, with negligible (<10ms) overhead from cuda transfer. Not sure what's going on with async-tiff, seems like the host to device overhead is larger, almost 140ms (maybe some copying is happening on the Bytes -> u8 -> DLPack conversion?
TODO