Add performance benchmark harness - #193
Open
raiseCatError wants to merge 3 commits into
Open
raiseCatError wants to merge 3 commits into
raiseCatError wants to merge 3 commits into
Conversation
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
1 participant
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.
The benchmark harness now applies to current dev and includes command-history scans/import at 10k and 100k, Bottom/Top/Flow ScreenPlan geometry, and chunked decoding of the current session protocol. The existing branch was updated by merging dev; published history is preserved. No runtime dependency or production behavior changes.
Measured baseline and investigation budgets are in docs/performance-benchmarks.md. History scan at 100k: p95 5.76ms; zsh import: 28.47ms; editor/layout/highlighting: 9.13ms. Whole-transcript wrapping/snapshot remain substantially slower and must stay outside per-keystroke query work. Live process startup and socket round-trip measurements remain deferred, explicitly distinguished from frame decoding.
Validation: build, typecheck, benchmark TypeScript check, all benchmark workloads and diff check pass. Full suite passes with inherited NO_COLOR removed; the first run failed color assertions because the execution environment exports NO_COLOR=1. No source changes were needed. Physical terminal QA is not required for this tooling change.
First/base PR for the v0.8 stack; do not merge during milestone development. #155 remains an open cross-milestone prerequisite, rather than claiming all its research is complete.
Refs #155