cherry: ws-head-latency sub-ms histogram floor + keyed slots (#1225) - #1226
Merged
Merged
Conversation
…#1225) Fix the leader-collapses-to-2.5ms artifact: histogram_quantile on a [0,5ms] first bucket interpolates every winner's p50 to ~2.5ms (chain-independent). Replace with a 0.5ms floor climbing to 10s so sub-ms wins actually resolve on Solana (~400ms slots) and Base (2s). Add keyed provider slots for Base (Alchemy/Infura/Chainstack/QuickNode) and Solana (Alchemy/Chainstack/Helius/QuickNode) so the cohort can extend beyond keyless once contributor keys are wired. Keyless tier is saturated on all three chains (audit failed: Ankr, Blast, LlamaRPC, BlockPI, 1RPC, NodeReal, Omniatech, base.org, extrnode, chainstack- public — none accepted a keyless WSS handshake as of 2026-07). Co-authored-by: Florent Tapponnier <contact@mobula.io>
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
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.
Cherry-pick of #1225 (currently on dev only) onto main so the fix ships to production Railway.
Why not merge dev → main
Dev is 20+ commits and ~6400 LOC ahead of main. The ws-head-latency bucket fix is a targeted correction (leader p50 collapses to ~2.5ms interpolation artifact) that shouldn't wait behind the broader dev backlog. Cherry lands only the bench-critical change.
What deploys after merge
Railway auto-redeploys 3 services from main:
ws-head-latency-usws-head-latency-euws-head-latency-sgpPost-merge
Purge
ws_head_lag_milliseconds_bucketfrom ocb-prom TSDB to drop the stale [0,5ms]-floored series (they'd collide with the new fine buckets and keep producing the 2.5ms artifact until they age out):curl -sX POST \ "http://ocb-prom:9090/api/v1/admin/tsdb/delete_series?match[]=ws_head_lag_milliseconds_bucket" curl -sX POST http://ocb-prom:9090/api/v1/admin/tsdb/clean_tombstonesTest plan