Dropwizard Jetty thread-pool and queue sizing for bursty concurrent traffic without latency spikes
I am configuring a Dropwizard service (assuming Dropwizard 2.x/3.x with the default embedded Jetty server) that must absorb short bursts of concurrent requests without the latency inflation that appears when the Jetty thread pool saturates and requests pile up in the bounded queue. The documented server.applicationConnectors and thread-pool settings ( minThr