Skip to content

docs(perf): whole-app before/after for #1475 (PM3) - #1487

Merged
currentbits merged 1 commit into
mainfrom
docs/perf-pm3-end-to-end
Oct 6, 2026
Merged

currentbits merged 1 commit into
mainfrom
docs/perf-pm3-end-to-end

Conversation

@currentbits

Copy link
Copy Markdown
Owner

End-to-end measurement of #1478–#1486. It compares a1c696aa, main just before the first fix, with 8b4bcc71, the same tree as nightly-202610060729-8b4bcc71. Both were measured in one session on the same frozen copy of today's data, using the PM1 and PM2 scenarios.

Headlines

  • Warm boot to sidebar rows: ≈1.34 s → ≈0.60 s, counting the login-shell PATH capture. Cold FCP: 520 → 316 ms.
  • Streaming: envelope writes 596 → 48 MiB per 30 s; main JS busy 2,644 → 436 ms; event-loop p99 back to the idle level.
  • threads:summaries cold: 1,669 ms → 8 ms. threads:changed: 2.68 MB → 1.3 KB.
  • files:resolve on a big-thread open: 614 → 4 IPCs.
  • Renderer streaming into the big open thread: blocked 48–69 → 0 ms/s; worst keypress→frame 102 → 13 ms.
  • Soak DOM after 6 streams: 61.6k → 13.0k nodes.
  • localStorage: 1,693 → 18 keys.

The report also lists what did not move: the big-thread switch is only −8%, soak RSS still climbs, and the main-heap LRU caps by count, not bytes.

Leak check: clean across 33 launches. The only ref diffs were commits by a live agent thread in another repo, each attributed by reflog.

Only the report commit is cherry-picked here. The worker's branch also carried two unrelated commits from a stale local HEAD.

🤖 Generated with Claude Code

Same-session measurement of a1c696a vs 8b4bcc7 on one frozen data
snapshot, using the PM1/PM2 scenarios and PM1's isolation recipe.
33 launches, no leak.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-06T09:22:21.497543Z e45a09a PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e45a09a544

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

| same, reopen | 1,589 (179 ms) | 8 (12 ms) |
| `threads:changed` from a rename, per push | 2,680,470 B; 3.5 ms send | 1,341 B; 0.02 ms send; 0.15 ms encoder diff |

Every `threads:changed` in these windows (run start, run end, rename) went out as a row patch. A full list only goes out on thread create, fork or reorder.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Include the first full thread-list push

On the first threads:changed event after each main-process launch, createThreadListEncoder() has no previous list and therefore sends { seq, threads: next }, so an ordinary first run-status update can still transmit the full ≈2.68 MB list. The row-patch result is thus steady-state behavior, not every status-change push as this sentence and the headline imply; document or measure the initial full push separately.

Useful? React with 👍 / 👎.

@currentbits
currentbits merged commit 35db9b2 into main Oct 6, 2026
11 of 12 checks passed
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