Add asv benchmark coverage for geotiff read/write paths#3603
Merged
Conversation
geotiff had no asv benchmark, so open_geotiff and to_geotiff had no regression coverage even though the module has dask and GPU backends. This adds benchmarks/benchmarks/geotiff.py. What it covers: - WriteGeoTIFF: to_geotiff on numpy, dask (the tile-row streaming writer), and cupy (the GPU writer) - WriteCOG: the cog=True overview-pyramid path on numpy and cupy - ReadGeoTIFF: open_geotiff decode on numpy and cupy (GPU decoder) - ReadGeoTIFFChunked: open_geotiff(chunks=) dask-backed read, materialized Each class writes a small temp GeoTIFF in setup and deletes it in teardown, so nothing depends on network fixtures. Two sizes, 512 and 2048, keep CI time down while still showing how each path scales. Benchmark-only, no source changes. I ran every class directly on a GPU host to confirm it works; the cupy paths ran for real, not skipped.
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
1 participant
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.
geotiff had no asv benchmark, so
open_geotiffandto_geotiffhad no regression coverage even though the module has dask and GPU backends. This addsbenchmarks/benchmarks/geotiff.py.What it covers:
WriteGeoTIFF:to_geotiffon numpy, dask (the tile-row streaming writer), and cupy (the GPU writer)WriteCOG: thecog=Trueoverview-pyramid path on numpy and cupyReadGeoTIFF:open_geotiffdecode on numpy and cupy (GPU decoder)ReadGeoTIFFChunked:open_geotiff(chunks=)dask-backed read, materializedEach class writes a small temp GeoTIFF in setup and deletes it in teardown, so nothing depends on network fixtures. Two sizes, 512 and 2048, keep CI time down while still showing how each path scales.
Benchmark-only, no source changes. I ran every class directly on a GPU host to confirm it works; the cupy paths ran for real, not skipped.