feat: uploadCarWithStat avoids copying stat.carBytes via Blob construction #2543
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.
… and instead wraps the stat.carBytes Uint8Array as a BlobLike
Context
Motivation:
new Blob
could get rid of a memory allocation that could be contributing to 'out of memory'uploadCAR
here and not a whole blob, there will not be downstream copies of the underlying bytes because this car BlobLike, once passed touploadCAR
will get passed to aCAR.BlockStream
that streams out blocks without re-buffering the whole car bytes in memory https://github.com/web3-storage/w3up/blob/main/packages/upload-client/src/index.js#L107