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

# Overview

This section provides comprehensive performance information for X Platform, including benchmarking results, test methodologies, and performance analysis.

## Performance Documentation

X Platform performance documentation is organized into two main sections:

### 1. Canonical Benchmark

The [Canonical Benchmark](/performance/canonical-benchmark.md) section presents results from the official end-to-end performance benchmark used to measure X Platform's core capabilities.

**What it measures**: Complete **Receive-Process-Send flow** of a clustered microservice, including messaging, state management, persistence, cluster replication, and consensus protocol.

**Key metrics**:

* **Wire-to-Wire Latency**: Time from inbound message arrival to outbound message transmission (50th, 99th, 99.9th percentiles)
* **Maximum Throughput**: Messages processed per second under saturated load

**Test program**: ESProcessor from the X Platform Performance Benchmark Suite

**Results available**: Performance metrics for X Platform 3.16 releases

➡️ [View Canonical Benchmark Results](/performance/canonical-benchmark.md)

### 2. Performance Benchmark Suite

The [Performance Benchmark Suite](/performance/benchmark-suite.md) section documents the collection of benchmarking tools that measure individual X Platform runtime components.

**What it includes**: 7 modules, each focusing on a specific component:

* **Time Module**: Time API overhead
* **Serialization Module**: Message encoding/decoding performance
* **Link Module**: Cluster replication transport
* **Messaging Module**: Pub/sub messaging layer
* **Persistence Module**: Message and data persistence
* **Storage Module**: Object store operations
* **AEP Module**: End-to-end canonical benchmark (described above)

**Purpose**: Isolate and measure individual component performance, understand performance characteristics, validate configurations

**Source code**: [github.com/neeveresearch/nvx-perf](https://github.com/neeveresearch/nvx-perf)

➡️ [Explore Benchmark Suite](/performance/benchmark-suite.md)

## Quick Start

### View Latest Results

See the latest canonical benchmark results:

* [X Platform 3.16.34 Performance](/performance/canonical-benchmark/test-results/3.16/3.16.34.md) - Latest tested release

### Run Your Own Tests

Download and run the benchmark suite:

1. **Download distribution** from the Neeve artifact repository:

   ```bash
   wget https://nexus.n5corp.com/repository/maven-public/com/neeve/nvx-perf-dist/3.16.34/nvx-perf-dist-3.16.34-linux-x86-64.tar.gz
   ```
2. **Extract and run**:

   ```bash
   tar xvf nvx-perf-dist-3.16.34-linux-x86-64.tar.gz
   cd nvx-perf-3.16.34
   $JAVA_HOME/bin/java -cp "libs/*" com.neeve.perf.aep.engine.ESProcessor --count 10000 --rate 5000
   ```
3. **See documentation** for detailed configuration and parameters:
   * [Test Description](/performance/canonical-benchmark/test-description.md) - Complete methodology
   * [Benchmark Suite Documentation](/performance/benchmark-suite.md) - All modules and tools

## Understanding Performance

### Latency Characteristics

X Platform is optimized for ultra-low latency:

* **Typical latency**: 27-30µs median (wire-to-wire, including network)
* **Tail latency**: 99.9th percentile within 1.5x of median
* **Configuration**: Performance varies by CPU configuration and optimization mode

### Throughput Characteristics

X Platform supports high-volume scenarios:

* **Typical throughput**: 280K+ messages/second per microservice instance
* **Scaling**: Linear scaling with message complexity and CPU resources
* **Configuration**: Best throughput with minimal CPU configuration for lightweight handlers

### Performance Factors

Key factors affecting X Platform performance:

1. **Message Access Method**: Direct access (serializer/deserializer) vs Indirect (POJO) - \~10% latency difference, 2.4x throughput difference
2. **CPU Configuration**: MinCPU, Default, or MaxCPU - affects parallelization vs coordination overhead
3. **Optimization Mode**: Latency or Throughput - different XVM and runtime tuning
4. **Hardware**: CPU, memory, storage (NVME vs SSD), network (InfiniBand vs Ethernet)
5. **Network Tuning**: VMA, RDMA enablement (not enabled in baseline tests)

## Next Steps

* [**Canonical Benchmark**](/performance/canonical-benchmark.md) - View official end-to-end performance results
* [**Benchmark Suite**](/performance/benchmark-suite.md) - Explore component-level benchmarks
* [**Test Description**](/performance/canonical-benchmark/test-description.md) - Understand test methodology in detail
* [**Test Results**](/performance/canonical-benchmark/test-results.md) - Browse results by X Platform release