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

# Benchmark Performance Results

This section details the performance characteristics of the Altius execution engine across two distinct environments: Raw Execution (theoretical maximum) and End-to-End (real-world application).

### Raw Execution Micro-Benchmarks (revm)

These metrics isolate the execution engine to measure maximum theoretical throughput for DeFi-heavy workloads using a dataset of 1,000 Uniswap transactions across 8 threads at a 0% conflict rate.

| Metric         | Sequential | Parallel + OCCDA | Parallel + SSA | Optimistic |
| -------------- | ---------- | ---------------- | -------------- | ---------- |
| Execution Time | 38.3 ms    | 5.89 ms          | 6.89 ms        | 3.01 ms    |
| Total Time     | 40.73 ms   | 12.08 ms         | 12.1 ms        | 8.28 ms    |
| TPS            | \~24.5k    | \~48.8k          | \~82.6k        | \~120.7k   |
| GPS (Mgas/s)   | 3,365      | 11,344           | 11,330         | 16,550     |
| Exec Speedup   | 1.0x       | 6.5x             | 5.56x          | 12.72x     |
| Conflict %     | 0%         | 0%               | 0%             | 0%         |

The optimistic strategy demonstrates a **12.72x speedup over standard sequential execution**, achieving near-linear scaling and processing over **16.5 Gigagas per second in isolation**.

### End-to-End Node Benchmarks

These tests evaluate performance in a realistic OP L2 node environment, measuring the full block processing pipeline including database I/O and state root calculation.

**Scenario A (Zero Conflict)**: In an ideal state with no transaction dependencies, parallel execution provides a 4.15x speedup in end-to-end latency.

<table><thead><tr><th>Strategy</th><th width="160.74609375">Server E2E Time</th><th>Client Latency</th><th>GPS (Ggas/s)</th><th>Speedup</th></tr></thead><tbody><tr><td>Sequential</td><td>148.04 ms</td><td>440.92 ms</td><td>0.69</td><td>1.00x</td></tr><tr><td>Parallel</td><td>43.57 ms</td><td>47.26 ms</td><td>2.86</td><td>4.14x</td></tr><tr><td>Optimistic</td><td>43.46 ms</td><td>46.95 ms</td><td>2.82</td><td>4.15x</td></tr></tbody></table>

**Scenario B (High Contention)**: With 50% of transactions conflicting, the engine maintains a 1.93x speedup over sequential processing.

| Strategy   | Server E2E Time | GPS (Ggas/s) | Speedup |
| ---------- | --------------- | ------------ | ------- |
| Sequential | 114.13 ms       | 1.09         | 1.00x   |
| Parallel   | 76.94 ms        | 1.61         | 1.55x   |
| SSA        | 89.99 ms        | 1.38         | 1.30x   |
| Optimistic | 64.58 ms        | 1.87         | 1.93x   |

The optimistic scheduler maintains superior performance even as conflicts rise, degrading gracefully while ensuring client latency remains stable. In realistic end-to-end scenarios, the system sustains between 1.8 and 2.8 Gigagas per second.

These results demonstrate that the **Altius architecture successfully shifts the bottleneck away from the CPU, allowing for a 2–4x performance boost on standard node infrastructure**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.altiuslabs.xyz/technical-overview/benchmark/benchmark-performance-results.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.