> ## Documentation Index
> Fetch the complete documentation index at: https://docs.loadforge.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Comparing Runs

> How to compare different test runs in LoadForge.

LoadForge makes it easy to **compare test runs** so you can track performance improvements, detect regressions, and analyze test history over time. There are two main ways to compare runs:

* **Runs Per Test View**: View all historical runs of a test in one place.
* **Compare View**: Directly compare two test runs side by side.

## Runs Per Test View

<Frame caption="Runs Per Test View">
  <img src="https://mintcdn.com/loadforge/-JPjrj7GdlQs4xIV/images/runs-per-test.png?fit=max&auto=format&n=-JPjrj7GdlQs4xIV&q=85&s=5cf6864906d848e94fd581983cd1c7cd" alt="Runs per Test" width="2316" height="1105" data-path="images/runs-per-test.png" />
</Frame>

The **Runs Per Test** page groups test runs by the specific test, allowing you to:

* See all historical runs for a particular test.
* Track **trends in performance, Apdex scores, error rates, and response times**.
* Identify how your application behaves under load over time.

<Tip>
  Use this view to spot trends. If Apdex scores or response times gradually degrade, your infrastructure may need optimization.
</Tip>

## Compare View

<Frame caption="Side-by-Side Run Comparison">
  <img src="https://mintcdn.com/loadforge/-JPjrj7GdlQs4xIV/images/runs-compare.png?fit=max&auto=format&n=-JPjrj7GdlQs4xIV&q=85&s=5260e5a234bb622f5193b5982bd16ccf" alt="Runs Compare" width="2314" height="589" data-path="images/runs-compare.png" />
</Frame>

LoadForge also provides a **side-by-side comparison** feature to analyze two test runs in depth. By selecting **"Compare"** on a test run, you can:

* **See key metric differences** (e.g., P95 response time, peak RPS, throughput changes).
* **Analyze response time trends** across both runs.
* **Compare request performance and error rates** to determine if optimizations were successful.
* **View side-by-side execution summaries** to pinpoint where performance improved or worsened.

### Key Metrics in Run Comparison

The comparison table highlights differences in:

* **Peak RPS (Requests Per Second)**
* **Peak Virtual Users (VUs)**
* **Average, P95, and Median Response Times**
* **Error Rate and Total Errors**
* **Peak Throughput**

<Tip>
  When comparing runs, focus on the trend lines rather than absolute numbers. A consistent pattern of improvement across multiple metrics is more meaningful than a single dramatic change in one area.
</Tip>

Visualizations such as **response time graphs, request per second trends, and error rates over time** help identify what changed between runs.

<Tip>
  A significant **drop in P95 response time** indicates a major performance improvement. Conversely, if P95 increases, investigate bottlenecks.
</Tip>

## When to Compare Runs

Comparing runs is particularly useful when:

* **Optimizing backend performance** (e.g., database queries, caching strategies).
* **Testing infrastructure changes** (e.g., scaling, new servers, load balancing adjustments).
* **Identifying regressions** after a code deployment.
* **Fine-tuning test configurations** to improve accuracy.

By leveraging LoadForge's **test history and comparison tools**, you can continuously optimize your application and ensure it scales effectively under load.

<CardGroup cols={2}>
  <Card title="Apdex Scoring" icon="gauge" href="/runs/apdex">
    Learn how Apdex scoring measures user satisfaction with performance
  </Card>

  <Card title="Run Results" icon="chart-line" href="/runs/run-results">
    Understand how to interpret detailed load test results
  </Card>
</CardGroup>