forked from mtusi2026/mtusi2026lab3
The LB queue does not move the peak of 8x1 (4526, 4677 and 4525 rps for maxconn 16, 32 and 64, overlapping ranges), and the pool moves it the other way: 4 connections per worker give 5358 rps, 16 give 3789, while the lock waiters grow from 14.7 to 102. So the pool is not short, extra connections only add writers to the hot chat row, which confirms the coordination cost of the USL fit. On the same CPUs 8x0.5 peaks 7 % below 4x1 and costs 15 % more CPU per request, so the retrograde 8x1 comes from the number of processes and connections, not from slower vCPUs. The report also names the cause of the flaky compose up, the WalSync stall of the dropped attempt, the disturbed control runs, and the evidence index gets a commit column for track 1. The scenario of the open change no longer presumes its own outcome. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V1d3RLHNBBMA6UqBLLJv27