> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/rt-lab/model-and-simulation/phasor-domain-with-ephasorsim/benchmarks.md).

# Performance Benchmarks - Copied

This section of the user documentation lays out some benchmarks for gauging system performance on the newest XG version of the OP5650 and OP5707 (including the new OPAL-RTLinux v3 operating system) being introduced in early 2021 versus their previous generation.

<table data-header-hidden data-search="false"><thead><tr><th></th><th></th><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>Benchmark</strong></td><td><strong>Minimum Time-Step</strong></td><td><strong>Performance Increase over Previous Generation</strong></td><td><strong>Model Availability</strong></td><td><strong>Minimum License Required</strong></td></tr><tr><td><a href="https://opal-rt.atlassian.net/wiki/spaces/PEUD/pages/144505820"><strong>Microgrid Based on IEEE 13-Node Test Feeder</strong></a></td><td>&#x3C;1 ms</td><td>109 %</td><td><p>In the software,</p><p>phasor18_MicroGrid.mdl</p></td><td>1,000 nodes</td></tr><tr><td><a href="https://opal-rt.atlassian.net/wiki/spaces/PEUD/pages/144505938"><strong>IEEE 39-Bus New England Power System</strong></a></td><td>&#x3C;1 ms</td><td>35 %</td><td><p>In the software,</p><p>phasor01_IEEE39.mdl</p></td><td>1,000 nodes</td></tr><tr><td><a href="https://opal-rt.atlassian.net/wiki/spaces/PEUD/pages/144505879"><strong>IEEE 123-Node Test Feeder</strong></a></td><td>&#x3C;1 ms</td><td>138 %</td><td><p>In the software,</p><p>phasor10_IEEE123.mdl</p></td><td>1,000 nodes</td></tr><tr><td><a href="https://opal-rt.atlassian.net/wiki/spaces/PEUD/pages/144505768"><strong>2000-Bus Synthetic Grid of Texas</strong></a></td><td>4.7 ms</td><td>N/A<br>(this benchmark can only run on 64-bit OS)</td><td><p>In the software,</p><p>phasor20_TEXAS.mdl</p></td><td>2,000 nodes</td></tr><tr><td><a href="https://opal-rt.atlassian.net/wiki/spaces/PEUD/pages/144437856"><strong>Modified IEEE 8500-Node Test Feeder</strong></a></td><td>&#x3C;1 ms</td><td>40 %</td><td><p>In the software,</p><p>phasor25_IEEE8500.mdl</p></td><td>10,000 nodes</td></tr><tr><td><a href="https://opal-rt.atlassian.net/wiki/spaces/PEUD/pages/144472367"><strong>10,000-Bus Synthetic Grid of WECC (USA)</strong></a></td><td>2.3 ms</td><td>17 %</td><td><p>In the software,</p><p>phasor21_10k_WECC.mdl</p></td><td>10,000 nodes</td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.opal-rt.com/docs/rt-lab/model-and-simulation/phasor-domain-with-ephasorsim/benchmarks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
