Skip to content

the sampling cadence in the published text was never 15 seconds - #2710

Closed
Flotapponnier wants to merge 2 commits into
mainfrom
fix/head-lag-cadence-text-main
Closed

Flotapponnier wants to merge 2 commits into
mainfrom
fix/head-lag-cadence-text-main

Conversation

@Flotapponnier

Copy link
Copy Markdown
Collaborator

the sampling cadence in the published text was never 15 seconds

The Success column divides by 2,880, and the scrape really is every 30 s:
one bnb series holds 2,877 samples over 24 h and consecutive samples sit
30 s apart, measured against prom.openchainbench.com on 2026-09-29. Two
published sentences said 15 s and 5,760 instead. That is the figure a
reader uses to check our own arithmetic, and it described a presence
ratio dividing by twice the truth.

The same answer page called GeckoTerminal a REST feed. It is not: the
monitor opens wss://cables.geckoterminal.com/cable and subscribes to an
ActionCable channel per pool. Its head lag is high for a different
reason, measured the same day at 53 s on bnb, 34 s on base and 11 s on
solana, within 1.5 s of each other in all three regions, so the delay
sits in their pipeline rather than in our transport.

The Success column divides by 2,880, and the scrape really is every 30 s:
one bnb series holds 2,877 samples over 24 h and consecutive samples sit
30 s apart, measured against prom.openchainbench.com on 2026-09-29. Two
published sentences said 15 s and 5,760 instead. That is the figure a
reader uses to check our own arithmetic, and it described a presence
ratio dividing by twice the truth.

The same answer page called GeckoTerminal a REST feed. It is not: the
monitor opens wss://cables.geckoterminal.com/cable and subscribes to an
ActionCable channel per pool. Its head lag is high for a different
reason, measured the same day at 53 s on bnb, 34 s on base and 11 s on
solana, within 1.5 s of each other in all three regions, so the delay
sits in their pipeline rather than in our transport.
The Success column divides by 2,880, and the scrape really is every 30 s:
one bnb series holds 2,877 samples over 24 h and consecutive samples sit
30 s apart, measured against prom.openchainbench.com on 2026-09-29. Two
published sentences said 15 s and 5,760 instead. That is the figure a
reader uses to check our own arithmetic, and it described a presence
ratio dividing by twice the truth.

The same answer page called GeckoTerminal a REST feed. It is not: the
monitor opens wss://cables.geckoterminal.com/cable and subscribes to an
ActionCable channel per pool. Its head lag is high for a different
reason, measured the same day at 53 s on bnb, 34 s on base and 11 s on
solana, within 1.5 s of each other in all three regions, so the delay
sits in their pipeline rather than in our transport.
@Flotapponnier

Copy link
Copy Markdown
Collaborator Author

Closing: already shipped. The corrected cadence text reached main through the
release merge #3021 on 2026-10-18.

All 3 substantial lines this PR adds are already present in main.

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