Skip to content

Commit f3a44db

Browse files
committed
docs(tcp): split the hosted failure rate between the two old checks
The hosted probe's 16 failures in 1,800 runs counted either old check. The batch rule failed about one run in 225 and the old throughput check about one run in 180; the status paragraph now says so.
1 parent f2fca4c commit f3a44db

1 file changed

Lines changed: 15 additions & 14 deletions

File tree

‎docs/PROJECT_STATUS.md‎

Lines changed: 15 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -175,20 +175,21 @@ unproven. Background compiler load is a hypothesis, not an established excuse.
175175
`tcp_reactor_perf` used to fail when a single batch took more than five
176176
times the median. On a loaded macOS host, an equivalent loop on OTP 29
177177
failed that rule too, and unchanged Nera builds failed it in roughly one
178-
run in 250. A per-round probe on hosted macOS runners found the same rule
179-
failing about one run in 110 with no round near 100 ms. There, bursts
180-
slowed many rounds a little, and the host paused the whole program for 20
181-
to 55 ms; one batch took 103 ms while its slowest round took 23 ms. Under
182-
full CPU load the probe also saw isolated rounds of 126 to 137 ms that a
183-
timer-driven process running alongside did not see. They sit just above
184-
the 125 ms period at which the macOS scheduler recomputes thread
185-
priorities, not near the reactor's 100 ms poll timeout; their cause is not
186-
proven. The test now times batches in microseconds and fails only when a
187-
stall or slowdown shows in at least two batches. Injected 100 ms stalls on
188-
every connection's first round, recurring 100 ms stalls, and a 1 ms
189-
slowdown per round from a connection's 300th or 600th round still fail it.
190-
One isolated pause does not, and neither does a real stall that happens
191-
only once per run.
178+
run in 250. A per-round probe on hosted macOS runners found that rule
179+
failing about one run in 225, and the old throughput check (sustained
180+
rounds over nine times the warmup) about as often, one run in 180, with no
181+
round near 100 ms. There, bursts slowed many rounds a little, and the host
182+
paused the whole program for 20 to 55 ms; one batch took 103 ms while its
183+
slowest round took 23 ms. Under full CPU load the probe also saw isolated
184+
rounds of 126 to 137 ms that a timer-driven process running alongside did
185+
not see. They sit just above the 125 ms period at which the macOS
186+
scheduler recomputes thread priorities, not near the reactor's 100 ms poll
187+
timeout; their cause is not proven. The test now times batches in
188+
microseconds and fails only when a stall or slowdown shows in at least two
189+
batches. Injected 100 ms stalls on every connection's first round,
190+
recurring 100 ms stalls, and a 1 ms slowdown per round from a connection's
191+
300th or 600th round still fail it. One isolated pause does not, and
192+
neither does a real stall that happens only once per run.
192193

193194
The test runner accepts exit 0 without proof of completion unless `%% EXPECT:`
194195
is supplied. P0-1 demonstrates why this is insufficient. Several reactor tests

0 commit comments

Comments
 (0)