Repository navigation
docs(bench): fork-vs-upstream 2026-10-27 — re-measured at 69af19ac - #555
Merged
Merged
Conversation
Re-measured the README comparison on current builds after the resolver reconciliation: upstream 69af19a vs fork bc27fdb, Node 24.22.1 and Bun 1.4.4, same seven pinned corpora. The picture changed enough that the old claims would mislead: the fork now loses five of seven index races (supabase 2.3x, n8n 2.4x — the ambient declare-module port, with the #554 memo bounding the quadratic but not the residual per-ref x per-file scan), wins every memory comparison, syncs faster on six of seven, and wins the n8n MCP cells except busy memory (+18% on Node). Tally: 56 better / 5 no-clear-change / 15 worse of 76. render-charts.mjs now classifies by each comparison's own run-to-run spread (house-rules #321) instead of the fixed 3% band, drops killed/failed rows, and says "slower"/"more" when the fork regresses instead of "0.4x faster". adapt-flat-output.mjs stages the current runner's flat output for the renderer. Contaminated n8n MCP attempt disclosed in the doc.
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
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
69af19acand the fork atbc27fdb4(post-perf(resolve): memoize ts_scope_scan — ambient-module lookup reparsed every .d.ts per import #554).declare moduleport; perf(resolve): memoize ts_scope_scan — ambient-module lookup reparsed every .d.ts per import #554's per-file memo bounded the quadratic, the per-ref × per-file scan remains). Faster sync on 6/7, less index memory on 7/7, n8n MCP wins except busy memory (+18% on Node).docs/benchmarks/fork-vs-upstream-node-bun-2026-10-27.mdcarries method, noise + contaminated-attempt disclosures, and the supabase-regression postmortem.render-charts.mjs: per-comparison spread classification (replaces fixed 3% band, per house-rules fix(resolve): JS/TS links across wrapped chains, comments, barrels, regexes and non-UTF-8 files #321), killed-row filtering, honest "slower"/"more" phrasing;adapt-flat-output.mjsbridges the current runner layout.Test plan
adapt-flat-output.mjs→render-charts.mjs)