Chunked HTTP get to avoid memory issues #761
Merged
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
maddenp-cu
commented
Jul 11, 2025
maddenp-cu
requested review from
christinaholtNOAA and
elcarpenterNOAA
as code owners
elcarpenterNOAA
approved these changes
Jul 14, 2025
christinaholtNOAA
approved these changes
Jul 14, 2025
maddenp-cu
added a commit
to maddenp-cu/uwtools
that referenced
this pull request
Jul 14, 2025
This was referenced Jul 14, 2025
Merged
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.
Synopsis
To avoid out-of-memory issues when fetching large remote files via HTTP, use streaming, chunked reads/writes instead of reading the entire file into memory and then writing it to disk. This should be an optimization invisible to users.
Type
Impact
Checklist