Top load testing metrics to follow | Gatling Datasheet
Datasheet · Load testing metrics

Top load testing metrics to follow: the 8 signals behind every bottleneck

What each metric measures, what it reveals, and how to read it, from request throughput and tail latency down to network and load generator signals. For performance engineering, platform, and QA teams.

Beyond pass/fail

Pass/fail tells you that something broke. Metrics tell you why.

Modern teams need more than pass/fail results. They need rich, contextualized metrics to diagnose bottlenecks and validate resilience at scale, from request-level behavior down to network and infrastructure signals.

These eight metrics cover three layers. Read them together, and you can tell a slow backend from a saturated network or an overloaded load generator.

The core metrics

Eight metrics, and how to read each one

Throughput, latency, and errors

01

Requests and responses per second

What it is

Tracks the volume of requests sent to the system and responses returned every second during a load test.

What it reveals

Throughput trends reveal system capacity under increasing load. If the request curve keeps rising while the response curve plateaus or drops, it usually signals thread pool exhaustion, backend saturation, or queue overflows.

Pro tip

Overlay throughput with concurrent users and error rates to find the exact inflection point where performance starts degrading.

02

Response time percentiles (p95 / p99)

What it is

Measures latency for the slowest users, typically the 95th and 99th percentiles, rather than averages.

What it reveals

Percentiles expose tail latency, which is what real users experience in worst-case scenarios. Averages can mask these spikes entirely. A rising p99 with a stable mean is a classic early warning sign of a regression.

Pro tip

Always track p95 and p99 during ramp-up and peak phases. Tail latency is what breaks SLAs and drives churn, not averages.

03

Errors per second and responses by status code

What it is

Monitors the volume of errors (such as 4xx and 5xx) per second and breaks responses down by HTTP status code.

What it reveals

Error spikes correlate strongly with system instability. 5xx surges after peak load point to capacity or dependency failures, while growing 4xx rates may reflect routing or client issues.

Pro tip

Slice errors by endpoint and scenario to find the root cause quickly. A sudden 5xx spike combined with flattening throughput often means the backend is collapsing.

Users and journeys

04

Virtual user metrics (arrival, termination, and concurrency)

What it is

Tracks how many users start (arrival), finish (termination), and are active at the same time (concurrency) during the test.

What it reveals

These metrics give a clear picture of load patterns and system response. Diverging arrival and termination curves often indicate slow transactions, timeouts, or abandoned sessions.

Pro tip

Use concurrency alongside response percentiles to pinpoint capacity ceilings. Unexpected drops in termination rate usually point to blocking issues.

05

Group duration percentiles

What it is

Measures the end-to-end duration of defined groups of requests, typically mapped to user journeys or business transactions such as checkout, search, or login.

What it reveals

Group metrics expose compounded latency across services and steps that single request timings miss. One slow API might not break an SLA, but several small delays add up quickly.

Pro tip

Use group percentiles to benchmark real business flows, so you prioritize the optimizations with the most customer impact.

Network and infrastructure

06

TCP connect duration percentiles

What it is

Measures the time taken to establish TCP connections from the load generator to the system under test.

What it reveals

Rising TCP connect times typically point to network or infrastructure bottlenecks, such as load generator saturation, exhausted connection pools, or firewall limits, before application performance visibly degrades.

Pro tip

Watch TCP connect percentiles during ramp-up. If they rise before response times do, the issue is likely outside the application layer.

07

TLS handshake duration percentiles

What it is

Tracks the duration of SSL/TLS handshakes while secure connections are established.

What it reveals

Handshake latency often becomes significant at scale, especially with CPU-heavy ciphers or certificate chain issues. Sudden increases during high-concurrency tests can add unexpected overhead.

Pro tip

Baseline TLS handshake times early and watch for spikes under load. They're often invisible in APM tools but visible in Gatling's client-side view.

08

Load generator infrastructure metrics (CPU and heap)

What it is

Monitors CPU usage and memory consumption on the load generators themselves, to make sure the test infrastructure can sustain the target traffic.

What it reveals

If generators hit CPU or heap limits, they become the bottleneck, adding artificial latency or failing to maintain target injection rates.

Pro tip

Always check generator health before blaming the system under test. Sustained CPU above 80% or heap usage above 85% can skew results dramatically.

How to go further

Connect test results, trends, and production telemetry

Once you track the core metrics, the next step is to connect individual test results with long-term trends and production telemetry.

Observe trends over time

See how your system evolves under pressure

Load testing isn't just about validating one release. Comparing performance across many runs reveals subtle regressions, capacity drift, and architectural bottlenecks that a single test misses.

Gatling Enterprise Edition's dashboards let you compare runs side by side and track key metrics over weeks or months, so you catch degradation before it becomes a production incident.

Correlate with APM and observability

Find the exact cause of a slowdown

Performance metrics gain their full diagnostic power next to infrastructure and application telemetry. Native integrations with Datadog and Dynatrace overlay load test data with real-time observability signals.

The correlation shows whether a slowdown comes from code, network saturation, database contention, or infrastructure limits, and gives developers, SREs, and QA one shared view.

Gatling Enterprise Edition

If load testing matters, your tool should too

Your users expect speed and reliability, and your load testing platform has to deliver the same. Gatling Enterprise Edition is built around five pillars.

Analyze smarter and act faster

Real-time visibility with dashboards, trend comparisons, and actionable insights.

Create tests your way

Code, low-code, or no-code: script in JavaScript, TypeScript, or Java, import Postman, or design visually.

Unlock automation

Trigger simulations from CI/CD or the API, apply stop criteria, and gate releases with performance thresholds.

Collaborate and share results

RBAC, SSO, quotas, and shared reports. Share results in Slack, Teams, or Jira.

Deploy load generators anywhere

Run tests from Gatling-managed regions, your own cloud, or on-prem.

Example Gatling test (JavaScript SDK)
import { constantUsersPerSec, scenario, simulation } from "@gatling.io/core"; import { http } from "@gatling.io/http"; export default simulation((setUp) => { // Define HTTP configuration const httpProtocol = http .baseUrl("https://api-ecomm.gatling.io") .acceptHeader("application/json"); // Define scenario const scn = scenario("Scenario").exec(http("Session").get("/session")); // Define injection profile and execute the test setUp(scn.injectOpen(constantUsersPerSec(2).during(60))) .protocols(httpProtocol); });
Ready to evaluate Enterprise Edition?

Keep the datasheet, or see it in action

Take all eight metrics and their pro tips to your team, or see them live in Gatling Enterprise Edition's dashboards.

Download

Get the full datasheet

All eight metrics, what each one reveals, and the pro tips to read them right.

PDF · free, no form Download the PDF
Live session

See Gatling Enterprise Edition live

A guided walkthrough with a Gatling engineer, with time for your questions.

Join the next live session