Skip to content

chore(sessions): attribute Codex per-rollout store waits - #4745

Closed
ScriptedAlchemy wants to merge 1 commit into
masterfrom
chore/4374-codex-admission-trace
Closed

ScriptedAlchemy wants to merge 1 commit into
masterfrom
chore/4374-codex-admission-trace

Conversation

@ScriptedAlchemy

@ScriptedAlchemy ScriptedAlchemy commented Nov 4, 2026 •

Copy link
Copy Markdown
Owner

Consolidated into #4742

Closed as superseded by the existing consolidated draft #4742 at commit 7a9f53506df27f122dbd872180656963cd3fbb4a.

The complete source head 9f2ae73dc4a9cdf8a8aa7c07e3bae8b429c65c36 is a parent of that integration commit. Both changed files were included byte-for-byte; the existing consolidation and its follow-up repairs were preserved. This source branch is retained. This is not a merge into master or a test-pass claim; combined-head Bazel validation remains required in #4742.

Scope

Refs #4374. The remaining project-scope Codex replay slowdown was measured at roughly 28 ms per unchanged rollout, but the existing top-level admission span does not attribute the store read/write and membership components separately. This change adds four trace-level timing boundaries around the existing operations:

  • Project rollout membership check (blocking worker).
  • Source cursor lookup (store authority).
  • Batched observation capture (store authority).
  • In-memory convergence settlement.

The current convergence-check and Codex admission spans remain intact. These nested timings let an operator compare project-scope reoffers using RUST_LOG and TRACEDECAY_SPAN_TIMINGS=1 before deciding whether the root cause is a per-rollout durable write, cursor lookup, blocking-worker scheduling, or something else. The shared JSONL admission spans also cover other providers without changing their contracts.

Safety and review

The exact admission operations, return values, cancellation/error handling, cursor state, scope matching, and store writes are unchanged. Source-reviewed as a two-file trace-only diff against master f64ec1f3. No new persistence authority, admission shortcuts, limits, or silent fallbacks.

Validation and limits

  • GitHub compared the pushed commit against the exact default-branch base: two files modified, no unrelated changes.
  • Bazel/Rust compilation, rustfmt, and focused tests not run here: the available execution environment has no Bazel or Rust toolchain. Hosted CI must validate the combined head in feat: consolidate pending TraceDecay changes #4742.
  • No measured performance improvement and no root-cause verdict claimed. This is the missing diagnostic boundary, not the speed fix. Follow-up: capture a real 2,010-rollout project-scope trace, reconcile per-file busy/idle timing, then fix the measured expensive operation.

Keep #4374 open; profile-scope fix #4380 is already merged but project-scope latency remains unresolved.

@changeset-bot

changeset-bot Bot commented Nov 4, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 9f2ae73

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

ScriptedAlchemy added a commit that referenced this pull request Nov 4, 2026
Integrate PR #4745 at 9f2ae73
into the existing #4742 draft, preserving both branch histories.

Both changed files matched the source PR's original blobs in the
consolidated tree, so retain the source blobs exactly without conflicts.
Only the four trace-level timing boundaries are added; existing storage,
LCM, search, SQLite lifetime repairs and release metadata stay unchanged.

This is consolidation into the draft branch, not a merge into master.
Source-reviewed only; combined-head hosted Bazel validation is still required.
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