Gatling HTML report limits in separating injector saturation from target latency
Gatling's asynchronous engine allows a single injector to sustain high request rates, yet the standard HTML report aggregates response-time percentiles and request counts without providing a definitive signal that distinguishes client-side queuing or resource exhaustion from genuine server-side latency. When an injector approaches its own limits—CPU saturati