Nine independent installed solver processes

Follow-up to the seven-process capacity shortfall, measured on the same existing Hetzner host on 2026-09-09. The production solver had zero active jobs before the run. No live fleet configuration or limits were changed.

Nine installed attested-relay-timelock==0.2.0a1 Linux x86-64 native processes each performed 50,000 genuine full-mode RandomX v2 hashes, with one worker and a separate dataset. A separate transient benchmark unit imposed CPUQuota=900%, Nice=10, CPUWeight=20, MemoryHigh=22G, MemoryMax=24G, MemorySwapMax=0 and TasksMax=128, with a 600-second hard runtime limit. The generalized runner is deploy/solver-fleet/benchmark-seven.py --workers 9 (accepted range 1–10).

All nine exited successfully within 170.02 seconds including dataset setup and polling. Peak charged memory was 22,126,710,784 bytes (20.61 GiB), with zero memory-high/max/OOM events and no swap. Dataset setup took 39.05–39.64 seconds.

This configuration clears the approximately 3,385 hashes/s break-even rate with 15.44% measured capacity margin. It addresses the observed steady-state backlog without additional hardware. This is a short-run estimate rather than a long-term availability or exact delay guarantee; outages, sustained unrelated workload and checkpoint overhead can consume that margin.

Hash intervals overlap almost entirely but start and finish slightly apart, so the aggregate is the sum of individually observed rates, not a synchronized multi-day measurement. Raw per-process durations, outputs, resource snapshots, binary digest, completion and summary are retained in processes-9-20260909/. The live fleet remained at seven workers / 700% CPU after this benchmark.