Increase Netty workerThreads or accept acceptor‑queue‑induced latency bursts under high concurrency?
The goal is to keep request latency low when a Ktor server handles many concurrent connections while preserving overall throughput. With the Netty engine, the default acceptor queue size caps the number of requests that can be processed simultaneously, and there is no stable API to adjust this queue independently of the worker thread count. Raising the worke