N8: 24-client network soak, and the server fixes it found
make soak runs a real server and 24 headless clients in three processes for two whole matches in real time. Each client reaches the server through its own UdpRelay, which adds 60 ms, +/-20 ms jitter and 2% loss each way, so ENet runs unchanged over a bad link. SoakPlayer drives each client from what a client knows: it drops, glides, heads for high ground, harvests and tries to build. tools/soak_report.gd checks world hashes against the server's, errors, unreadable packets, every client playing every match with its connection intact, memory between matches, and the p99 tick with the network's share. make soak-selfcheck proves a drifted client world is caught. Server changes: --matches=N, --world-hash-every=N, tick timing that includes after_tick, and memory in match and progress lines. What the soak found and fixed: - Snapshot building for 24 clients took the p99 tick to 13.8 ms, over the 12 ms budget, against a 2.8 ms simulation. Encoded records are now shared between clients for the tick, unchanged records skip the field diff, and clients are spread over the snapshot interval by handle. p99 is 7.3 ms. - ENet peers had a timeout limit of 0, which gives up on a peer as soon as any reliable message has waited the minimum timeout. Now ENet's default, 32. Not fixed: one or two clients still lose their connection about 15 s into the second match's drop in each run (see the issue), so the soak still fails and N8 stays open. Refs #39 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -28,6 +28,14 @@ const MSG_WELCOME: int = 2
|
||||
const MSG_REJECT: int = 3
|
||||
|
||||
## Why a connection ended. Sent in REJECT and as disconnect data.
|
||||
## ENet's timeout limit for every peer: a reliable message is given up on after this
|
||||
## many round-trip timeouts' worth of resends (and at least the peer's minimum timeout),
|
||||
## or after its maximum timeout. ENet's own default. 0, which this once was, gives up as
|
||||
## soon as any reliable message has waited the minimum timeout: over a link losing 2%
|
||||
## of datagrams each way, a run of unlucky resends then dropped a few soak clients a
|
||||
## match (issue N8).
|
||||
const PEER_TIMEOUT_LIMIT: int = 32
|
||||
|
||||
const REASON_NONE: int = 0
|
||||
const REASON_VERSION: int = 1
|
||||
const REASON_FULL: int = 2
|
||||
|
||||
Reference in New Issue
Block a user