Skip to content

Conversation

@petrosagg
Copy link
Contributor

Since the reclock operator stores the reclock bindings in time order and we restrict IntoTime to be a total order we can perform compaction in a much cheaper way and only when necessary.

Motivation

Tips for reviewer

Checklist

  • This PR has adequate test coverage / QA involvement has been duly considered. (trigger-ci for additional test/nightly runs)
  • This PR has an associated up-to-date design doc, is a design doc (template), or is sufficiently small to not require a design.
  • If this PR evolves an existing $T ⇔ Proto$T mapping (possibly in a backwards-incompatible way), then it is tagged with a T-proto label.
  • If this PR will require changes to cloud orchestration or tests, there is a companion cloud PR to account for those changes that is tagged with the release-blocker label (example).
  • If this PR includes major user-facing behavior changes, I have pinged the relevant PM to schedule a changelog post.

Since the reclock operator stores the reclock bindings in time order and
we restrict `IntoTime` to be a total order we can perform compaction in
a much cheaper way and only when necessary.

Signed-off-by: Petros Angelatos <petrosagg@gmail.com>
@petrosagg petrosagg marked this pull request as ready for review November 24, 2025 20:51
@petrosagg petrosagg requested a review from a team as a code owner November 24, 2025 20:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant