Skip to content
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.

Updated on June 15, 2020

System requirements for public networks

To determine system requirements, check 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 8GB.

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 750GB of disk space. Full synchronization requires approximately 3TB.

AWS requirements

We are running 1.4.5 mainnet nodes using t3.large boxes.

We synchronized the 1.4.5 mainnet nodes using t3.xlarge 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 that 1.4.5, resource requirements may have increased.

Questions or feedback? You can discuss issues and obtain free support on Hyperledger Besu chat channel.
For Hyperledger Besu community support, contact the mailing list besu@lists.hyperledger.org