โ† Back to 30-Day Challenge

๐Ÿ”— Correlation & Realism ยท Days 13โ€“18

Day 16: Pacing & Arrival Rate

Objective

Model a target requests-per-minute using pacing or arrival-rate mode.

Scenario

Set a target of 600 requests per minute (10/sec). Use your tool's pacing or arrival-rate feature. Run and compare achieved rate vs target rate.

Metrics to Watch

arrival rate vs achieved rate

When It Clicks

The tool can't hit a rate the system can't sustain - gaps reveal limits.

Solution

In JMeter: add a Constant Throughput Timer set to 600 samples/min, mode 'All active threads (shared)'. The timer will add delay to keep the aggregate rate at target. If the system can't sustain the rate, the timer has no effect and throughput lags - this gap is the capacity ceiling. In k6: use `scenarios.constant_arrival_rate` with `rate: 10, timeUnit: '1s'`. Watch 'dropped_iterations' in the k6 output - any non-zero value means the system could not fulfill the target rate.

Reflection

When the achieved rate fell below target, what was the bottleneck?

Deliverable

An arrival-rate or paced script with a target throughput.

โš ๏ธ Never run load tests against infrastructure you do not own or have explicit written permission to test. Always use a dedicated test environment. Unauthorized load injection can cause outages, trigger legal liability, and violate terms of service.