Load Runner
Stress-test any request with bounded concurrency. The Load Runner sends the same request N times, controls how many are in-flight at once, and surfaces live performance metrics as it runs.
Configuration
- Total requests — how many times to send the request in total.
- Concurrency — how many requests can be in-flight simultaneously.
- Per-iteration delay (optional) — milliseconds to wait between dispatching each request.
Each iteration re-resolves {{random}}, {{timestamp}}, and all other dynamic variables, so every request in the run is unique.
Live Metrics
While a run is in progress the metrics panel updates in real time:
- Sent count, remaining count, and requests per second (RPS)
- Latency percentiles: p50, p95, p99
- Overall success rate (percentage)
- Status code histogram — e.g. 200, 201, 400, 500, and any other codes encountered
- Error kind breakdown — timeout, connection refused, TLS error, etc.
Response Validator
Optionally configure pass/fail criteria before starting a run:
- Expected status codes — a comma-separated list such as
200, 201. Any response outside this set is flagged as a validation failure. - Body contains — an optional substring that must appear in the response body. Requests where the body does not contain this string are flagged.
Validation failures appear in the console log as yellow rows, distinct from network errors (red) and successes (green).
Controls
- Start — begins the run with the configured parameters.
- Stop — halts the run mid-way. Partial results and metrics collected so far are preserved and remain visible.
The console log at the bottom of the panel shows one row per completed request, color-coded:
- Green — request succeeded and passed validation.
- Yellow — request completed but failed the response validator check.
- Red — network-level error (timeout, refused, TLS failure, etc.).