aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/dashboard.md22
1 files changed, 17 insertions, 5 deletions
diff --git a/docs/dashboard.md b/docs/dashboard.md
index 0b1b10d..72d77da 100644
--- a/docs/dashboard.md
+++ b/docs/dashboard.md
@@ -140,11 +140,23 @@ at one speed: over a longer link they arrive later. Each follows the line it wen
a PING or PONG of the paths layer, which names the address it went to, the line of
that address's transport (curved, beside the one in use); any other, the line in use.
They come from the node's message log as it goes: the node sends what it logged a tenth
-of a second after the first of them, so a message runs soon after it went, and the
-messages of a moment start as far apart as they were sent. Of more than 6 in a moment
-on a link and way, 6 run, shared out by message kind, spread over the moment; each kind
-in its colour (named in the legend; the console colours them alike). After a gap (the
-computer slept, the stream stalled), only the last 2 s of what then comes runs. A dot
+of a second after the first of them. Each node's stream comes its own way, a subscribed
+node's over the network to it, so they arrive later than this node's, each by its
+path. So messages run not as they arrive but when they went, on one timeline: each at
+the time its node logged it, taken back by how far that node's clock is ahead of this
+node's (as the map chains the clocks), a while behind real time. How far behind
+(`behind: …` after the sliders) is the most any stream lagged within the last 30 s and
+a tenth of a second more; its tooltip shows how it came about (which node's stream
+lagged the most, by how much, and the margin) and the three slowest streams, each with
+the most and the least it lagged, so a slow path shows. Lags are measured by the
+browser's clock against this node's: one that is off adds to all of them alike. Messages of different nodes then run as far apart as they went,
+give or take how well their clocks are known (within the bounds the clock chain has). A
+message the page knows only from its receiver (its sender's messages aren't read: not
+subscribed) arrives at the time its receiver logged it, starting a crossing before.
+Of more than 6 at once on a link and way, 6 run, shared out by message kind, spread
+over the moment; each kind in its colour (named in the legend; the console colours
+them alike). Messages lagging more than 10 s (after a gap: the computer slept, a stream
+stalled) don't run. A dot
is as large as its message (by the size's logarithm: a ping small, a large sync message
large; shared out, as its kind's messages on average); the `size` slider
right after their legend makes all dots larger or smaller, and the `speed` slider after