Repository navigation
the 0 ms was 0.3 ms, rounded away - #3015
Merged
Merged
Conversation
Where the zero came from, exactly: QuickNode's median on the block-push cohort is 0.3 ms, and every formatter on this page rounded to the nearest millisecond below one second. A third of a millisecond printed as "0 ms", which tells the reader a provider answered instantly. It was not confined to the race. The same rounding flattens 0.6 and 1.4 into "1 ms" across the p90 and p95 columns, and on the HTTP cohorts it turns 2.1 against 5.8 into 2 against 6, erasing the gap the board exists to show. So below 10 ms the figure keeps one decimal, in all three formatters: the chain table, the provider pivot, and the summary card, which carried the same zero under "Smallest push lag". Above 10 ms the tenths are noise and the rounding stands. The pivot also gets what the chain table got earlier today: on the race cohort its "Median p50" is a median LAG behind whichever provider pushed the block first, so it is headed "Median lag" there, with a tooltip saying the leader sits near zero because it is zero behind itself and that the number to read is the trailers' distance from it. Gates: tsc clean, eslint clean, 561 tests.
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
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.
the 0 ms was 0.3 ms, rounded away
Where the zero came from, exactly: QuickNode's median on the block-push
cohort is 0.3 ms, and every formatter on this page rounded to the nearest
millisecond below one second. A third of a millisecond printed as "0 ms",
which tells the reader a provider answered instantly.
It was not confined to the race. The same rounding flattens 0.6 and 1.4 into
"1 ms" across the p90 and p95 columns, and on the HTTP cohorts it turns 2.1
against 5.8 into 2 against 6, erasing the gap the board exists to show.
So below 10 ms the figure keeps one decimal, in all three formatters: the
chain table, the provider pivot, and the summary card, which carried the
same zero under "Smallest push lag". Above 10 ms the tenths are noise and
the rounding stands.
The pivot also gets what the chain table got earlier today: on the race
cohort its "Median p50" is a median LAG behind whichever provider pushed the
block first, so it is headed "Median lag" there, with a tooltip saying the
leader sits near zero because it is zero behind itself and that the number
to read is the trailers' distance from it.
Gates: tsc clean, eslint clean, 561 tests.