Files
tidewall/test/sim
claudeandClaude Opus 5.5 ad0fd2695d H12: Build the next match's island on a worker thread
When a match's results begin, Match starts the next match's Simulation on a
WorkerThreadPool task (its seed is fixed by then) and collects it when the
lobby opens. The same task plans the island's tide levels
(Simulation.plan_tide) and runs a prepare_next hook, which ServerLoop uses
to build the bots' NavGrid and BotWorld for the island. All of these read
only the new simulation, so the results are the ones the main thread would
have made: tests compare the state hash, terrain, solids, props, tide
levels and navigation with fresh ones, and the ten-matches test still
matches its references. A Match freed while its task runs waits for it.

Measured: a 24-bot server paced in real time through the results, lobby,
countdown and 3 s of the next drop has a worst tick of 5.4 ms; it was 1.8 s.
In the 24-client soak at 2% loss, moving the island alone left a 0.82 s tick
(the bots' navigation) and moving that too left 74 ms at the next match's
start (planning the tide), which this also moves. The soak hasn't been run
again since that last step.

Closes #79

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-13 01:27:39 -05:00
..
2026-11-11 20:48:41 -05:00
2026-11-11 20:48:41 -05:00
2026-11-11 14:11:15 -05:00
2026-11-11 17:19:45 -05:00
2026-11-11 20:48:41 -05:00
2026-11-11 20:16:20 -05:00
2026-11-11 20:24:00 -05:00
2026-11-10 14:47:10 -05:00
2026-11-10 14:47:10 -05:00
2026-11-10 14:47:10 -05:00
2026-11-11 20:48:41 -05:00
2026-11-11 20:48:41 -05:00
2026-11-11 12:24:50 -05:00
2026-11-11 12:24:50 -05:00