Skip to content

Fix stale full pipeline benchmark numbers in README#1079

Merged
brendancol merged 1 commit into
masterfrom
issue-1077
Mar 28, 2026
Merged

Fix stale full pipeline benchmark numbers in README#1079
brendancol merged 1 commit into
masterfrom
issue-1077

Conversation

@brendancol
Copy link
Copy Markdown
Contributor

Summary

  • NumPy pipeline time updated from 2.7s to 784ms (was 3.4x too slow, predates reproject/geotiff optimizations)
  • rioxarray pipeline time updated from 418ms to 749ms (hardware/version drift)
  • GPU rows left unchanged (no GPU available to re-measure)

Closes #1077

Test plan

  • Verify numbers by running the pipeline benchmark (read 3600x3600 Copernicus DEM + reproject to EPSG:3857 + write GeoTIFF)

NumPy was listed as 2.7s but measures ~784ms after recent reproject
and geotiff optimizations. rioxarray updated from 418ms to 749ms
to reflect current measurement on the same workload.
@github-actions github-actions Bot added the performance PR touches performance-sensitive code label Mar 28, 2026
@brendancol brendancol merged commit fe12cd2 into master Mar 28, 2026
10 of 11 checks passed
@brendancol brendancol deleted the issue-1077 branch May 4, 2026 13:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

performance PR touches performance-sensitive code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

README full pipeline benchmark numbers are stale

1 participant