Skip to content

Foundations

This section builds the mental model you need to run, read, and act on load tests in MaxoPerf. Every concept here is illustrated with examples from the MaxoPerf console — not abstract theory.

The Foundations section covers the building blocks of performance testing in the order you need them: what performance testing is, how it differs from other testing disciplines, what the key metrics mean, and how to interpret a finished run.

Work through the pages in order the first time. Later you can jump to any page as a reference.

OrderPageWhat you will learn
1What is performance testing?The goal of performance testing and when to use it.
2Performance vs other testingHow load testing fits alongside functional, integration, and security tests.
3Core metrics explainedLatency, throughput, RPS, error rate, concurrency — what they are and how to read them.
4Latency percentiles deep diveWhy averages mislead and how p50/p90/p95/p99 give a true picture.
5Virtual users and concurrencyThe difference between VUs, concurrency, and request rate.
6Open vs closed workload modelsArrival-rate (open) vs VU-count (closed) — when each fits.
7Ramp-up, think time, and pacingHow to shape a realistic load profile.
8Baselines, SLOs, and error budgetsReliability framing — what “good” looks like and how to defend it.
9How much load do you need?Sizing and estimation math: from traffic data to VU count.
10Choosing safe test environmentsStaging vs production — authorization, blast radius, and test isolation.
11Anatomy of a load test resultA full tour of a MaxoPerf run-detail page and what every panel tells you.

No prior performance-testing experience is required. You should be comfortable with HTTP request/response basics (status codes, headers, payloads). If you have not yet run your first test in MaxoPerf, Run your first test is a ten-minute guided walk-through — come back here once the first run has finished.

After completing this section, move on to:

  • Test types — the taxonomy of load tests (smoke, load, stress, spike, soak) and which to reach for in each situation.
  • By engine — Taurus YAML, JMeter JMX, and k6 scripts in MaxoPerf.
  • Cookbook — step-by-step recipes for common performance-testing scenarios.

Last updated: