Skip to content

speed test on production, the RPC map stays off (dev side) - #2745

Closed
Flotapponnier wants to merge 2 commits into
devfrom
feat/speedtest-and-map-on-prod-dev
Closed

Flotapponnier wants to merge 2 commits into
devfrom
feat/speedtest-and-map-on-prod-dev

Conversation

@Flotapponnier

@Flotapponnier Flotapponnier commented Sep 30, 2026 •

Copy link
Copy Markdown
Collaborator

Same commits as #2744 (against main), on dev so the two branches do not diverge.

/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 Flotapponnier changed the title speedtest and RPC map on production (dev side) speed test on production, the RPC map stays off (dev side) Sep 30, 2026
@Flotapponnier

Copy link
Copy Markdown
Collaborator Author

Superseded: dev was synced with main after #2748 (06eef42).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant