mirror of
https://github.com/hanzoai/benchmarks.git
synced 2026-10-30 14:59:11 +00:00
MEASURED.md said memory is deterministic and has no range. On a host at load average 3 it is: 573.0 MB and 601 bytes per agent, twelve for twelve, byte-identical across three separately built binaries. On a second host at load 17 to 73 the same lane read 594, 595, 596 and 599. Two things differ between those and this pass cannot separate them — the machines are not the same machine, and only one was busy. The cross-machine part is already known, an M1 Max and an M4 Max differ by about five bytes here. So the line now says what was observed and not a cause: determinism under quiet conditions, about 1% of variation under load, unresolved. AND THE LANES NOW SAY WHICH THEY WERE. host.sh, say.mjs and goroutine/main.go all print the one-minute load beside the CPU and core count, because a reader cannot tell a busy machine from a quiet one after the fact and this is exactly the distinction the paragraph above turns on. While wiring it: MEASURED.md claimed "every lane that measures time prints its host", and fleet, sandbox and pricing printed none at all — platform.mjs harvests lane output by looking for that very line, so it recorded no host for any of the three. say.mjs has the function now and all three call it, so the sentence is true of both halves. Co-authored-by: Hanzo Dev <[email protected]>