Skip to content

sync: bring ws-head-latency harness + parent bench 081 + multi-region to main#1199

Merged
Flotapponnier merged 1 commit into
mainfrom
chore/cherry-ws-head-multi-region-main
Jul 16, 2026
Merged

sync: bring ws-head-latency harness + parent bench 081 + multi-region to main#1199
Flotapponnier merged 1 commit into
mainfrom
chore/cherry-ws-head-multi-region-main

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

Consolidates the ws-head-latency cluster on main. Includes the harness (was dev only), parent bench 081, and the region ConstLabel patch from #1198. After merge, create Railway ws-head-latency service with 3 replicas + OCB_REGION env.

…on support to main

Consolidates 3 dev merges (#1170 harness + #1196 per-chain benches + #1198 multi-region) so main matches dev on the ws-head-latency cluster:

  * benchmarks/ws-head-latency.yml: parent bench 081 (Ethereum)
  * benchmarks/ws-head-latency-base.yml: bench 087, adds regions arrays
  * benchmarks/ws-head-latency-solana.yml: bench 088, adds regions arrays
  * harnesses/ws-head-latency/: full harness (was dev only), including
    region ConstLabel from OCB_REGION or RAILWAY_REPLICA_REGION
  * railway.toml: Railway build config so the service can be created

After merge, create the Railway ws-head-latency service with 3 replicas
(us-east, eu-west, sgp), set OCB_REGION on each. Railway auto-builds
from main, metrics start flowing per region.
@Flotapponnier
Flotapponnier merged commit e5b9be8 into main Jul 16, 2026
@Flotapponnier
Flotapponnier deleted the chore/cherry-ws-head-multi-region-main branch July 16, 2026 11:14
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