docs(apiproxy): state the export queue bound exactly

The response stream uses a fixed 64 KiB byte high-water mark; no deployment setting controls it. Calling that queue configured incorrectly suggested another tuning surface and obscured the concrete memory bound.\n\nName the fixed capacity directly while preserving the separate bound of one synchronous fflate push beyond the queued bytes.
This commit is contained in:
Tianyi Cui
2026-08-11 17:47:29 +08:00
parent 8d63728584
commit 5e067fa7fe

View File

@@ -15,7 +15,7 @@
* bytes are produced incrementally and the host never holds the whole archive
* in one buffer; production waits for consumer pull whenever the response queue
* reaches its byte high-water mark, so a slow consumer bounds accumulation to
* the configured queue plus one synchronous fflate push.
* the fixed 64 KiB response queue plus one synchronous fflate push.
* @module
*/