# Performance

- [Hardware requirements](https://docs.x1.xyz/validating/performance/hardware-requirements.md)
- [Ping validator](https://docs.x1.xyz/validating/performance/ping-validator.md): Running Pinger allows the validator to share leader data transmission times with the network.
- [Node maintenance](https://docs.x1.xyz/validating/performance/node-maintenance.md)
- [Disk IOPS test](https://docs.x1.xyz/validating/performance/disk-iops-test.md): Purpose: check that your validator’s disk is fast enough for X1 block production. This test safely benchmarks random read/write performance (IOPS) using the fio tool.
- [Validator health check](https://docs.x1.xyz/validating/performance/validator-health-check.md): This script runs a full system health report for your X1 validator: it checks CPU, Memory, Disk I/O, Network latency, Clock synchronization, and Vote Account activity — all in one run.
- [Validator bandwidth test](https://docs.x1.xyz/validating/performance/validator-bandwidth-test.md): Test your validator's bandwidth: download/upload speeds, live throughput, and RPC connectivity.


---

# Agent Instructions: 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.x1.xyz/validating/performance.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.
