The guide said `in_flight = 64 x pods_ready`. 64 was the configured
ceiling; the measured capacity is ~32 (`Running: 29-32 reqs, Waiting: 0`
on every pod of a live fleet), and the 0.557 pages/s per pod the guide
quotes was itself measured at a concurrency of 32.

Offering 64 does not queue inside the orchestrator. It queues in the
pod's socket backlog, and an overflowing backlog makes a healthy pod
refuse connections -- which on 2026-10-19 got eight A40s terminated
mid-work with 522 pages on them. v0.4.37 stops the termination; this
stops the overload that triggered it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KnfkxBpcZ1v6ypRFFyhrVM