Ktor Netty Engine: Server vs Client EventLoopGroup Sharing Decision
When a Ktor application hosts both an HTTP server and a client using the Netty engine, the default configuration creates separate EventLoopGroup instances for each pipeline. This can lead to thread overhead or contention under high concurrency, yet the framework does not expose a straightforward API to enforce sharing of a single group across both engines. T