Repository navigation
Conversation
…perf harness The #425 harness only drove Classic with an empty session, so it could not measure #417's gates for Next or the cost #439 is about. - --ui next selects the Next renderer; Classic runs set no selector, so they stay comparable with the recorded baseline. - --history-lines N resumes a synthetic session. A resume must prove it loaded, because a failed one falls back to an empty session and would measure as a very fast long conversation. - --stream runs a turn against a fake claude and reports input-to-paint and the gap between paints during it. Refs #417, #439
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Extends the #425 performance harness to measure Next, long transcripts and running turns, and records the first matched Classic and Next results. It finds that Next on main fails #417's memory gate at 100,000 lines, and that #440 fixes it.
Context
Changes
--ui nextselects Next. Classic runs set no selector, so they stay comparable with the test(tui-tests): add raw PTY performance baseline harness #425 baseline.--history-lines Nresumes a synthetic session. A resume must prove it loaded, because a failed one falls back to an empty session and would look like a very fast long conversation. Next must show seeded text; Classic must print the CLI's load confirmation, because its 80x24 welcome header can leave no transcript rows.--streamruns a turn against a fakeclaudein the disposable home, then reports input-to-paint during the turn and the gap between paints.Results
No history
100,000 transcript lines
Each cell is the range across both sizes (80x24, 120x40) and both passes, using each profile's summary from 5 runs. Each 100,000-line Next profile has about 100 key samples per run set and about 575 paint gaps. The two passes ran in opposite order to expose load drift. Classic at 100,000 lines has no turn figures because of #441.
Against #417's gates
What this says about #440
Limits
3f73b63(sha2565fd76a57), feat(tui): keep Next transcript rows between frames and add jump to start (#439) #4406f16a8a(sha25653f55406). macOS 27.2, Apple M5 Max, rustc 1.99.1.Validation
python3 -m unittest discover -s scripts/tui-tests -p 'test_*.py': new tests failed first, then pass.--streamat 100,000 lines (20 of 20, Classic transcript height wraps past 65,535 rows, hiding the live end of the conversation #441).git diff --check: clean.cargo fmt/check/clippy/test; no Rust changed.Refs #417, #439