Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] compute: spillable MV correction buffer #30083

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

teskje
Copy link
Contributor

@teskje teskje commented Oct 18, 2024

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.

@teskje teskje force-pushed the correction-lgalloc branch 2 times, most recently from ffdf64d to 77afd64 Compare October 21, 2024 08:31
@teskje teskje force-pushed the correction-lgalloc branch 2 times, most recently from 25b0987 to 0b2e359 Compare October 25, 2024 12:13
@teskje teskje force-pushed the correction-lgalloc branch 4 times, most recently from ffb5488 to 4697f9c Compare November 25, 2024 10:22
This commit introduces a "correction v2" buffer that differs from the
existing one in that it stores data in columnated regions that can be
spilled to disk. It follows the general design of the arrangement merge
batcher, with the major difference that it sorts updates by time first,
in an attempt to more efficiently deal with the presence of updates in
the future (commonly introduced by temporal filters).
This commit adds a new dyncfg, `enable_compute_correction_v2`, that
controlls whether the MV sink v2 should use the old or the new
implementation of the correction buffer.
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.

2 participants