You are reading Hyperledger Besu development version documentation and some displayed features may not be available in the stable release. You can switch to stable version using the version box at screen bottom.
Date of last update: August 24, 2022

# System requirements

Determine public network system requirements by checking CPU and disk space requirements using Prometheus. Grafana provides a sample dashboard for Besu.

Tip

CPU requirements are highest when syncing to the network and typically reduce after the node is synchronized to the chain head.

## Java Virtual Machine size

For Mainnet and testnets, the minimum Java Virtual Machine (JVM) memory requirement is 8 GB.

JVM memory requirements are highest when syncing, but will reduce after the node is synchronized to the chain head. Monitor your system to determine your actual JVM memory needs.

## Disk space

Fast synchronization with pruning enabled requires approximately 750 GB of disk space. Full synchronization requires approximately 3 TB.

## Disk type

Use local SSD storage for high throughput nodes (validators and RPC nodes). Read-only nodes can use a lower performance setup.

You can use local SSDs through SCSI interfaces. For higher performance in production settings, we recommend upgrading to NVMe interfaces.

## AWS requirements

We are running 22.4.2 Mainnet nodes using m6gd.2xlarge boxes.

We synchronized the 22.4.2 Mainnet nodes using m6gd.2xlarge boxes.

Using a larger box while synchronizing speeds up the sync process by giving it more resources. When the sync is completed, the box size can be reduced.

Important

If you are using a more recent release than 22.4.2, resource requirements may have increased.