chore(benchmarks): drop solana-tx-landing-latency - #701
Merged
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Flotapponnier added a commit
that referenced
this pull request
Jun 25, 2026
…benchmarks payload) (#706) * chore(benchmarks): drop solana-tx-landing-latency (harness offline, 404 bleeding SEO) (#701) * perf(benchmarks): slim card projection cuts /benchmarks payload 3.2MB to 280KB (#704) * fix(types): widen isInsufficient to accept BenchmarkCardData slim shape Cherry-pick fallout: #704 introduced BenchmarkCardData (slim projection for the hub) but main's isInsufficient still required full Benchmark. The hub card calls isInsufficient(b) where b is the slim type, which typecheck rejected. Widening the predicate input to a structural subset lets both Benchmark and BenchmarkCardData pass without losing the runtime behavior.
Flotapponnier added a commit
that referenced
this pull request
Jun 27, 2026
…ge (#766) Drop in #701 (2026-06-25) was driven by harness offline + 404 SEO. The Railway harness still runs and Prom keeps emitting solana_landing_probe_enabled=1 plus the slot/latency series, so restoring the YAML brings the page back live (or in 'awaiting samples' until a funded SOLANA_PROBE_KEYPAIR_BASE58 is set on Railway). Validate clean (34 specs).
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 freeto 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.
Why
/benchmarks/solana-tx-landing-latencycurrently returns 404 + noindex. Google still has it in the sitemap and is hitting it (top 3 page impressions in GSC), so it bleeds SEO every day.The active-probe Solana harness is offline and not getting redeployed soon, so cleanest fix is to remove the bench entirely from the repo. If we ship it again later we redo it properly.
What changes
Deletes:
benchmarks/solana-tx-landing-latency.yml(the spec)alternatives/helius.yml,alternatives/jito.yml(both pointed at this bench, orphaned otherwise)answers/which-solana-rpc-lands-the-most-transactions.yml(same, orphaned answer)docs/methodology/solana-tx-landing-active.md(pre-registered methodology for the active probe)Edits:
src/data/bench-published.json: remove the slug entrysrc/data/compare-pairs.ts: remove thehelius-sender-vs-jitopair (only existed because of this bench)src/app/answers/page.tsx+src/app/answers/[slug]/page.tsx: drop the slug from inline doc commentsharnesses/solana-tx-landing/README.md+ the three.gofiles: remove dangling references to the deleted methodology doc and second bench. The observationalsolana-tx-landingbench keeps using the same harness binary, the active-prober code stays in the repo for future re-enablement.Validation
pnpm validatepasses (33 specs)pnpm typecheckpassespnpm lintclean (5 pre-existing warnings, unrelated)git grep -in solana-tx-landing-latencyreturns 0 matches post-commit