Skip to content

sync: cherry-pick ws-head-latency per-chain benches 087/088 (#1196)#1197

Merged
Flotapponnier merged 1 commit into
mainfrom
chore/cherry-ws-head-latency-per-chain-main
Jul 16, 2026
Merged

sync: cherry-pick ws-head-latency per-chain benches 087/088 (#1196)#1197
Flotapponnier merged 1 commit into
mainfrom
chore/cherry-ws-head-latency-per-chain-main

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

Cherry-pick of #1196 from dev. Per-chain siblings ws-head-latency-base + ws-head-latency-solana. No harness changes: data flows from the Paris VPS today.

Per-chain siblings of bench 081 for the WebSocket head-lag cluster.
Same harness (harnesses/ws-head-latency), same race scoring, one
spec per chain to avoid mixing block cadences (Ethereum 12s vs Base
2s vs Solana 400ms) in a single leaderboard.

Base cohort: PublicNode + dRPC keyless endpoints. Tenderly does
not expose a keyless Base WebSocket path.

Solana cohort: PublicNode + Solana Foundation. slotSubscribe
replaces newHeads on the harness side; metric names are shared so
the queries are structurally identical to the EVM specs.

Data already flows via the Paris VPS deployment (chain label carries
base and solana). No harness change needed for this ship. Multi-region
is a follow-up on the parent bench.

Co-authored-by: Florent Tapponnier <contact@mobula.io>
@Flotapponnier
Flotapponnier merged commit beaa79f into main Jul 16, 2026
@Flotapponnier
Flotapponnier deleted the chore/cherry-ws-head-latency-per-chain-main branch July 16, 2026 11:03
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