> For the complete documentation index, see [llms.txt](https://docs.loadmill.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.loadmill.com/performance-testing/overview.md).

# Overview

Loadmill performance testing replays API scenarios at scale so you can measure how a system behaves under concurrent traffic. A performance test can be created directly or derived from an API flow that already represents real application behavior.

## What you can validate

Use performance tests to:

* Measure response times, throughput, and error rates under load.
* Validate expected capacity before a release or high-traffic event.
* Find requests or services that become bottlenecks as concurrency increases.
* Compare system behavior across environments or application versions.
* Add performance thresholds to a repeatable delivery workflow.

## Typical workflow

1. Create a scenario or convert an existing API flow.
2. Run a dry run to confirm that one iteration succeeds.
3. Configure duration, concurrency or request rate, ramp-up behavior, and execution locations.
4. Verify ownership of the tested domains before running at higher volume.
5. Run the test and review the results for latency, throughput, and failures.

## Get started

Follow the [Performance Testing Quickstart](/get-started/getting-started-1.md), learn how to [configure a load test](/performance-testing/working-with-the-test-editor.md), or review how to [analyze performance test results](/performance-testing/analyzing-load-test-results.md).