Repository navigation
docs: back the speed claim with the fitted rate model, not a single example - #1113
Merged
Merged
Conversation
Contributor
2 tasks done
…xample Replaces "a handful of 20M+ LOC outliers take a few minutes instead" with the actual fitted two-regime model from gitgalaxy-raw-output's 599-repo batch: flat ~0.11s below ~4,258 LOC (fixed overhead dominates), then time(s) ~= 3.36e-05 * LOC^0.969 above it (R^2=0.88, near-linear rather than degrading on large inputs). Both the knee and the exponent are derived from the batch data (compute_rate_model() in that repo), not eyeballed. Embeds the LOC-vs-time chart in "Proof, Not Just Claims" item 3, pulled from gitgalaxy-raw-output's self-updating speed_charts/latest/ path so it never goes stale here -- no manual re-embedding needed on future releases. Logged in docs/readme_evidence_roadmap.md's Shipped table per the readme-maintenance process. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
squid-protocol
force-pushed
the
docs/speed-proof-raw-output
branch
from
August 7, 2026 00:17
632e1fb to
5610287
Compare
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
Follows up on the work just done in
gitgalaxy-raw-output(PRs #6-9 there): a two-regimescan-speed model fit directly from its 599-repo v2.4.6 batch, plus a self-updating
LOC-vs-time chart. This PR brings that evidence into
gitgalaxy's own README perdocs/how_to_maintain_the_readme.md's rules (every superlative needs a number + link;proof before benchmarks).
outliers take a few minutes instead" (no number, no link) with the actual fit --
time(s) ≈ 3.36e-05 × LOC^0.969above ~4,258 LOC (R²=0.88, 599 repos), flat ~0.11s belowit -- linking to Proof for the chart and derivation.
from
gitgalaxy-raw-output's self-updatingspeed_charts/latest/loc_vs_time.pngpath, soit never needs manual re-embedding as new versions land there.
docs/readme_evidence_roadmap.md's Shipped table per the readme-maintenanceskill's process (step 5: log what unlocked/shipped in the same PR).
Kept the existing Kubernetes single-example sentence (still a real, concrete number) --
this adds the aggregate model alongside it rather than replacing a good example with an
abstraction.
Test plan
gitgalaxy-raw-output's mergedmainbefore embedding0.11s,4,258 LOC,3.36e-05,0.969,R²=0.88)directly against that repo's live
speed_charts/latest/rate_model.txthow_to_maintain_the_readme.md's five rules: numbers+links present,no bare superlatives, no new emoji, section order unchanged (edits are within existing
sections, Proof still precedes Benchmarks)
🤖 Generated with Claude Code