satellite/metainfo: reduce pointerDB access for CommitObject #3589
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.
What: Currently CommitObject is iterating from
s0
tosN+1
to detect last segment and renamesN
tol
. CommitObject request contains objectmetadata
andnumberOfSegments
which can be used to determine index of last segment without iterating. Only oneGet
is needed to acquire pointer bytes for deletion.Backward compatibility concerns:
CommitObject method was merged with uplink on Sep 10 (#2640 ) and unencrypted segment count was merged on Aug 22 (#2859 ) so we can assume that all clients that are using CommitObject are also storing unencrypted segment count in object metadata.
Why: Less request to
pointerDB
, faster execution.Please describe the tests:
Please describe the performance impact: more segments are committed faster execution compared to current implementation
Code Review Checklist (to be filled out by reviewer)