Repository navigation
speed test on production (the RPC map stays off) - #2744
Closed
Flotapponnier wants to merge 2 commits into
Closed
Flotapponnier wants to merge 2 commits into
Flotapponnier wants to merge 2 commits into
Conversation
/speedtest-rpc and /rpc-map were held off production in DEV_ONLY_ROUTES since 2026-09-21 (2 cells, 32 samples: not ready for an audience). Removing them from the list serves both pages on production, with their four /api/speedtest routes, and links them again from the sitemap, llms.txt and the /rpc hub, which all read the same list. Contributions go to the same Redis store the rest of the site already uses in production.
… it there /rpc-map goes back in DEV_ONLY_ROUTES: only the speed test ships. Its results panel said each run was "added to the global latency map" and linked to /rpc-map, which answers 404 on production. The page now tells the client whether the map is served; without it the panel says the result was added to the crowdsourced latency data and shows no link. Contributions continue either way, so the map has data the day it ships.
Flotapponnier
changed the title
Collaborator
Author
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.
What
Serves
/speedtest-rpc(browser RPC speed test) on production./rpc-mapstays off production.Both were held in
DEV_ONLY_ROUTES(src/lib/removed-benches.ts) since 2026-09-21 ("2 cells, 32 samples: not ready for an audience"). The speed test leaves the list; the map stays in it. The speed test page, its contribute API, its sitemap entry, itsllms.txtline and the link from the/rpchub all read that list, so they come back together.Fix in the speed test
Its results panel said each run was "added to the global latency map" and linked to
/rpc-map, a 404 on production. The page now tells the client whether the map is served (mapLive); without it, the panel says the result was added to the crowdsourced latency data and shows no link. Contributions continue either way (same Redis store the rest of the site uses), so the map has data the day it ships.Verified
tsc --noEmitclean, eslint clean on the touched files,bun test src/lib346 pass. The same commits are ondevin #2745.