Seven independent installed solver processes
Measured on the existing Hetzner host on 2026-09-09, while the live production
solver daemon had zero active solver jobs. The installed public Linux x86-64
wheel was attested-relay-timelock==0.2.0a1; its native binary digest is retained
in seven-20260909/environment.json.
Seven separate full-mode calibration processes each performed 50,000 genuine RandomX v2 hashes with one worker and their own dataset. A separate transient systemd unit imposed the live fleet's CPUQuota=700%, Nice=10, CPUWeight=20, MemoryHigh=18G, MemoryMax=20G, MemorySwapMax=0 and TasksMax=128. Runtime was bounded to 600 seconds. Live fleet units were not stopped or changed.
All seven processes exited successfully within 160.02 seconds including dataset setup and polling. Peak charged memory was 17,212,116,992 bytes (16.03 GiB), with zero memory-high/max/OOM events and no swap. The production solver, mirror and tunnel remained running with zero restarts afterward.
| Quantity | Result |
|---|---|
| Per-process hash rates | 422.49, 434.04, 446.76, 423.34, 436.05, 424.92, 456.26 /s |
| Aggregate hash rate | 3,043.86 /s |
| Hashes in one production puzzle | 306,376,868 |
| Individual puzzle recovery estimate | 7.77–8.39 days |
| Sustainable aggregate epoch cadence | 27.96 hours |
| Measured production generation cadence used for comparison | 25.14 hours |
| Solver capacity / production rate | 89.92% |
At these rates the seven-process fleet accumulates roughly 0.0963 epochs of backlog per day, or one additional epoch every 10.4 days. It has insufficient capacity for the measured production cadence. The earlier single-process rate therefore did not establish sustainable fleet capacity.
These are short-run estimates, not delay guarantees. Dataset setup completed at slightly different times (37.20–39.13 seconds), so each process's hash interval overlapped almost entirely but not exactly. Rates include brief startup contention and faster trailing work as peers finish. Long-term load, outages, checkpoint overhead and changes in generation speed remain unmeasured. The aggregate cadence uses the sum of per-process hash rates; including setup in the entire short run would give a conservative 2,187.26 hashes/s that is not representative of a multi-day puzzle's negligible setup fraction.
Raw per-process JSON, stderr, resource snapshots, completion and computed summary
are retained in seven-20260909/. The runner is
deploy/solver-fleet/benchmark-seven.py; no core solver code was modified.