Choosing Between Open and Closed Workload Models in Gatling
Learn how to choose between Open and Closed workload models in Gatling to avoid coordinated omission and simulate realistic user traffic for APIs and internal systems.
Loading…
ReadMeFeed / Community knowledge
#load-testing
Real questions. Useful conversations. Find the people who know your stack.
CSV Feeders in Gatling: Data‑Driven Authentication Tests Made Simple
Data‑driven authentication tests in Gatling are easy with CSV feeders. Learn how to set up per‑user feeders, avoid contention, and validate your results in this practical guide.
gatlingControlling Concurrency in Gatling with the Closed Model
Learn how Gatling's Closed Model maintains fixed concurrent virtual users for predictable load testing, and when to use it instead of the Open Model.
Controlling Request Rates in Gatling: Injection Profiles vs. Throttling
Learn how to choose between injection profiles, throttling, and pacing in Gatling to maintain a steady target RPS without distorting latency measurements.
Diagnosing k6 Virtual User Saturation: When the Load Generator Becomes the Bottleneck
High response times with a calm target server often mean your k6 load generator is saturated. Learn how to diagnose VU memory pressure and right-size your test.
Enforcing Trust Boundaries in Gatling with Response Checks
Learn how to use Gatling HTTP response checks to create trust boundaries, preventing invalid data propagation and ensuring load test accuracy.
Diagnosing Gatling Connection Errors During Load Test Ramp-Up
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.
Gatling Feeder Strategies: Realistic Data Without the Hall of Mirrors
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 Builds with k6 Thresholds and abortOnFail
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.
k6