the gate warning compared requests against pages (v0.4.26)
The diagnostic added in 0.4.25 tested `gate * 4 < ocr.max_concurrency`. Those
are different units -- a request against a page -- and for the 4096-page budget
this install runs it demanded a gate of 1024: memory-unsafe, and four times
more than the derivation in the same function will ever choose. It therefore
fired against the 256 that derivation had just picked, telling the operator to
raise a value coderai itself had chosen as correct:
[queue] max_parallel_requests=256 max_size=2048
[queue] WARNING: ... admits only 256 request(s) ... Raise
server.max_parallel_requests ...
The floor and the cap are now named once, as _GATE_FLOOR and _GATE_CAP, and
both the derivation and the warning read them, so the two rules cannot
disagree again -- a separate literal in each place is how they came to.
The warning now tests the gate's own size rather than its ratio to a page
budget, which is also the only thing worth saying: a handful of admitted
requests cannot feed a pod pool whatever the page budget is. Since an unwritten
key is already derived above the floor, it now reaches only an explicitly small
value, and says so.
Co-Authored-By:
Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KnfkxBpcZ1v6ypRFFyhrVM
Showing
Please
register
or
sign in
to comment