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

# Test Results

This section contains performance benchmark results for Rumi releases. Results are organized by major release version, with detailed results provided for each specific release tested.

## Organization

Performance results are structured as follows:

* **Release Line** (e.g., Rumi 4.0) - Groups results for a major release line
  * **Specific Release** (e.g., Rumi 4.0.579-4.0.39) - Contains actual test results for that release (Core version - Bindings version)

## Available Results

### Rumi 4.0

* [Rumi 4.0.579-4.0.39](/performance/canonical-benchmark/test-results/4.0/4.0.579-4.0.39.md) - Core: 4.0.579, Bindings: 4.0.39 (February 2025)

## Understanding the Results

Each release results page includes:

### Latency Results

* 50th, 99th, and 99.9th percentile latencies in microseconds
* Results for both Indirect and Direct message access methods
* Results across MinCPU, Default, and MaxCPU configurations
* Latency-optimized configuration results

### Throughput Results

* Maximum messages per second under saturated load
* Results for both Indirect and Direct message access methods
* Results across MinCPU, Default, and MaxCPU configurations
* Throughput-optimized configuration results

### Performance Analysis

* Key performance characteristics
* Optimal configurations for different use cases
* Tuning recommendations
* Comparisons with previous releases (where applicable)

## Test Methodology

All results are generated using the same canonical benchmark described in the [Test Description](/performance/canonical-benchmark/test-description.md). This ensures:

* **Consistency** - Direct comparability across releases
* **Reproducibility** - Same hardware, configuration, and methodology
* **Transparency** - Full disclosure of test parameters

## Next Steps

* View [Test Description](/performance/canonical-benchmark/test-description.md) for complete test methodology
* Select a release above to view detailed results
* Return to [Canonical Benchmark Overview](/performance/canonical-benchmark.md)
* Explore [Performance Benchmark Suite](/performance/benchmark-suite.md) for the full benchmark suite


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.rumi.systems/performance/canonical-benchmark/test-results.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.