[8.1.0] Reduce retention and early materialization of VirtualActionInput
#25008
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.
b82dcdc introduced a way for parameter files to be materialized lazily and in a streaming fashion. For this to be effective, the contents of
VirtualActionInput
s should not be retained and, ideally, never or only briefly materialized in full.This is achieved by replacing the digest computations with a streaming approach and avoiding retention of
VirtualActionInput
inMerkleTree
s, which may be cached. All cache protocols are streamlined to accept aBlob
, which is a closeable supplier ofInputStream
s that is automatically closed after the upload has completed (which may require retries).Along the way, file nodes in
MerkleTree
s are stored unwrapped to reduce memory usage.Closes #24891.
PiperOrigin-RevId: 718042524
Change-Id: I1567cf6ca36cbf5e1146c91df34157c9192bb822