> 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/benchmark-suite/modules.md).

# Modules

The Rumi Performance Benchmark Suite consists of seven specialized modules that benchmark individual components of the Rumi platform:

## Individual Component Benchmarks

* [**Time Module**](/performance/benchmark-suite/modules/time-module.md) - Benchmarks time acquisition overhead for different time sources
* [**Serialization Module**](/performance/benchmark-suite/modules/serialization-module.md) - Measures message encoding and decoding performance
* [**Link Module**](/performance/benchmark-suite/modules/link-module.md) - Tests cluster replication link throughput and latency
* [**Messaging Module**](/performance/benchmark-suite/modules/messaging-module.md) - Benchmarks the SMA messaging layer
* [**Persistence Module**](/performance/benchmark-suite/modules/persistence-module.md) - Measures persistence mechanisms for messages and data
* [**Storage Module**](/performance/benchmark-suite/modules/storage-module.md) - Benchmarks object store operations

## End-to-End Benchmark

* [**AEP Module**](/performance/benchmark-suite/modules/aep-module.md) - The canonical end-to-end benchmark measuring the complete Receive-Process-Send flow

The AEP Module is used to generate Rumi's official performance metrics published in the [Canonical Benchmark Results](/performance/canonical-benchmark.md).

## Next Steps

* Review the [Performance Benchmark Suite Overview](/performance/benchmark-suite.md) for information on releases, distributions, and running benchmarks
* View [Canonical Benchmark Results](/performance/canonical-benchmark.md) for published performance metrics


---

# 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/benchmark-suite/modules.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.