ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When Gatling KO% spikes during ramp-up with connect timeouts, connection refused, or too many open files while the target looks healthy, the issue is usually injector socket exhaustion or target accept-queue overflow.
Identical requests can make a Gatling load test look busy while measuring nothing. Choose a feeder strategy that matches your endpoint's uniqueness needs, and verify it in the simulation log.
Fail CI pipelines automatically when k6 load tests breach latency or error‑rate SLOs by defining thresholds, using abortOnFail, and tagging requests. This guide shows how to set up, run, and verify thresholds in CI.
Inject data into Gatling scenarios with a CSV feeder. Learn how to configure, stream, and avoid common pitfalls so your load tests run reliably and efficiently.
Learn how to shape the request rate of a Gatling test with the throttle injection profile, including setup, verification steps, and common recovery actions.
k6 thresholds turn vague "looks fine" load testing into enforced performance budgets. Here's how to scope them per endpoint, gate CI on the exit code, and avoid flaky failures.
Learn how Gatling’s injection profiles let you shape traffic patterns, from sudden spikes to steady streams, and why the right choice matters for realistic load testing.
Learn why k6 thresholds may silently ignore pass/fail conditions and how to diagnose placement, metric collection, and early‑test termination issues.
Open vs. Closed Injection in Gatling – a concise decision guide that maps constraints, compares profiles, explains trade‑offs, and shows a concrete simulation with validation steps.
gatling
k6