feat: Use remote.Reuse to make everything faster #2929
Merged
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.
Summary
Continuing #2901
Previously, every call to a remote.Function was performing a Ping and Token exchange, which meant that we were doing 3 round trips instead of 1 (for most calls).
The remote.Reuse option effectively tells the remote package to call methods on a Pusher/Puller instance rather than re-doing the Ping and Token requests.
The alternative to this PR would be to plumb around a puller and pusher instance and refactor all of cosign to call methods on those, but this is much simpler.
For an empty destination repository,
cosign copy
improved from 24s to 19s. When re-running it against a repository we already pushed to, we see improvement from ~12s to ~3.5s.cosign copy gcr.io/projectsigstore/cosign:v1.13.0 (before)
cosign copy gcr.io/projectsigstore/cosign:v1.13.0 (after)
Release Note
cosign
registry operations were optimized to be much faster.Documentation