Repository navigation
perf(runs): measure runs search before and after the per-day index - #39
Merged
Merged
Conversation
6,000 synthetic runs over 30 days, generated through cli-messaging's own startRun. A missed --error-code went from 1.76 s to 16 ms; free-text search still reads events (2.3 s -> 1.35 s). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Task
CLI standards, stream C step 4: time
runs searchbefore and after its index on a generated 30-day run folder.Why
The index PR in cli-messaging needs its numbers recorded where results live, with the script that produced them.
What
performance/runs/search-index/README.md: why, setup, results, what it showed, what was not measured.generate.mjs(6,000 synthetic runs through the build'sstartRun) andbench.mjs(median of 11 rounds).performance/runs/README.mdlinks it.Headline: a missed
--error-code1.76 s → 16 ms;runs list31 ms → 0.7 ms; free-text miss 2.3 s → 1.35 s (still reads events).Testing
Both scripts run against the before and after builds;
biome checkandmarkdownlint-cli2clean.🤖 Generated with Claude Code