Skip to content

exec: separate tickers of logging and membatch-size-check #21125

Merged
AskAlexSharov merged 2 commits into
mainfrom
worktree-exec3-commit-ticker
May 13, 2026
Merged

exec: separate tickers of logging and membatch-size-check #21125
AskAlexSharov merged 2 commits into
mainfrom
worktree-exec3-commit-ticker

Conversation

@AskAlexSharov

@AskAlexSharov AskAlexSharov commented May 12, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • LogInterval (20 s) was controlling both progress-log emission and membatch size checks in the serial executor
  • Split into two tickers: logEvery (20 s) for LogExecution() only, and checkIsBatchFullEvery (5 s) for the batch-full check
  • A full membatch now triggers a commit within 5 s instead of up to 20 s
  • The parallel executor is unaffected — it already checks batch size inline after every block result (event-driven, no ticker needed)

…ial executor

LogInterval (20s) was driving both progress logs and membatch size checks.
Split them: logEvery (20s) for logs only, commitEvery (5s) for the batch-full
check so a full membatch triggers a commit within 5s instead of up to 20s.
@AskAlexSharov AskAlexSharov changed the title execution/stagedsync: separate log and membatch-commit tickers in serial executor alex: separate log and membatch-commit tickers in serial executor May 12, 2026
@AskAlexSharov AskAlexSharov changed the title alex: separate log and membatch-commit tickers in serial executor exec: separate tickers of logging and membatch-commit tickers in serial executor May 12, 2026
@AskAlexSharov AskAlexSharov changed the title exec: separate tickers of logging and membatch-commit tickers in serial executor exec: separate tickers of logging and membatch-commit tickers May 12, 2026
@AskAlexSharov AskAlexSharov changed the title exec: separate tickers of logging and membatch-commit tickers exec: separate tickers of logging and membatch-commit May 12, 2026
@AskAlexSharov AskAlexSharov changed the title exec: separate tickers of logging and membatch-commit exec: separate tickers of logging and membatch-size-check May 12, 2026
@AskAlexSharov AskAlexSharov requested a review from JkLondon May 12, 2026 05:59
@yperbasis yperbasis requested a review from Copilot May 12, 2026 10:40

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This pull request improves serial execution responsiveness by decoupling progress logging from the periodic “membatch full” check, allowing full batches to trigger a commit check more frequently without increasing log volume.

Changes:

  • Added a new 5s ticker in the serial executor to check whether the state batch is full.
  • Kept the existing 20s ticker dedicated to LogExecution() only.
  • Ensured periodic commitment/commit checks can be triggered sooner when the batch reaches its size threshold.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@yperbasis yperbasis added the UX label May 12, 2026
@AskAlexSharov AskAlexSharov added this pull request to the merge queue May 13, 2026
Merged via the queue into main with commit aa2523e May 13, 2026
101 of 107 checks passed
@AskAlexSharov AskAlexSharov deleted the worktree-exec3-commit-ticker branch May 13, 2026 02:03
AskAlexSharov added a commit that referenced this pull request May 13, 2026
@sudeepdino008

Copy link
Copy Markdown
Member

membatch-size-check -- it can be done after every block exec too -- it's relatively cheap.

sudeepdino008 pushed a commit that referenced this pull request May 13, 2026
## Summary

- `LogInterval` (20 s) was controlling both progress-log emission and
membatch size checks in the serial executor
- Split into two tickers: `logEvery` (20 s) for `LogExecution()` only,
and `checkIsBatchFullEvery` (5 s) for the batch-full check
- A full membatch now triggers a commit within 5 s instead of up to 20 s
- The parallel executor is unaffected — it already checks batch size
inline after every block result (event-driven, no ticker needed)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants