Skip to content
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

Speed-up geolocation-array based warping of Sentinel3 datasets #10812

Merged
merged 6 commits into from
Sep 27, 2024

Conversation

rouault
Copy link
Member

@rouault rouault commented Sep 16, 2024

Fixes #10809

Timing back from ages (half an hour or so) to 20 seconds.
Also fixes a bug related to Int64/UInt64 VRT bands with nodata.

@coveralls
Copy link
Collaborator

coveralls commented Sep 16, 2024

Coverage Status

coverage: 69.371% (+0.003%) from 69.368%
when pulling 642f7cc on rouault:fix_10809
into ce6bae8 on OSGeo:master.

GDALCopyWords(&paSrcData[idxBuffer], eSourceType, 0,
abyTemp, eVRTBandDataType, 0, 1);
CopyWord(&paSrcData[idxBuffer], eSourceType, abyTemp,
eVRTBandDataType);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rouault From what I understand, for single-word copies with zero stride on both source and dest, you replaced calls to GDALCopyWords with calls to CopyWord which improved performance.

In #11254 I noticed that there is a 0 stride single word copy just below your change (rasterio.cpp:3402), do you think it might be worth doing the same replacement on more places in the source code? And what was the reason the next line in this file wasn't also replaced with a call to CopyWord?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The CopyWord() method cannot be applied on the next line, because it relies on compile-time known source type, whereas in below line eVRTBandDataType is a runtime-known data type.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

perf: gdalwarp 3.4.3 takes seconds, gdalwarp 3.5.0 and later takes 30+ minutes
3 participants