aboutsummaryrefslogtreecommitdiffstats
path: root/docs/measurements.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-03 02:43:43 +0100
committertv <tv@krebsco.de>2026-11-03 02:43:43 +0100
commit8f0b588831ac06913dd01a3ebd8bb523292d992e (patch)
tree8e40f658c7a5f63cfc748fad9905490f64613d3b /docs/measurements.md
parent5cd26d321b706113afb8431aba35ab8fb32281c4 (diff)
skip neighbours with our heads
Diffstat (limited to 'docs/measurements.md')
-rw-r--r--docs/measurements.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/measurements.md b/docs/measurements.md
index fb01de0..131adca 100644
--- a/docs/measurements.md
+++ b/docs/measurements.md
@@ -137,7 +137,7 @@ growing is the sign, and that writer's own `clock.off` ([`trust.md`](trust.md),
clocks"). Writers aren't known by node (Automerge's actors are per run), so their skew
can't be taken off too. With sane clocks: in a full mesh most
changes land in the first buckets; in a partial mesh each hop adds about a round trip
-plus the 200 ms announcement delay. Mass in the minutes buckets means changes arrive by
+plus the announcement delay (200 to 400 ms). Mass in the minutes buckets means changes arrive by
keepalive-triggered pulls rather than relay, i.e. announcements are being lost.
## Clocks