Updated 2020-03-20

System requirements

The system requirements for Hyperledger Besu depend on different factors, including the:

  • Size of the world state for the network.
  • Number of transactions submitted to the network.
  • Block gas limit.
  • Number and complexity of JSON-RPC, PubSub, or GraphQL queries handled by the node.

Determining system requirements

To determine system requirements, check CPU and disk space requirements using Prometheus. Grafana provides a sample dashboard for Besu.


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


Besu requires 4GB of RAM. For public Ethereum networks, including MainNet and testnets such as Ropsten, Besu requires a minimum of 8GB of RAM.

Disk space


Do not use pruning in Hyperledger Besu v1.4.0. Pruning has a known bug.

If using fast sync in v1.4.0, explicitly disable pruning using --pruning-enabled=false.

Syncing to the Ethereum Mainnet requires 3TB for a full sync. To reduce the disk space required, use pruning. With pruning, we recommend approximately 750GB of available disk space.

VM requirements

You can run Besu on a virtual machine (VM) on a cloud service, such as AWS or Azure, or locally using a VM manager, such as VirtualBox.

If you set up your own VM locally using a VM manager, there are a few considerations:

  • Ensure you enable Intel Virtualization Technology (VTx) and Virtualization Technology for Directed I/O (VT-d) in the BIOS settings.
  • On Windows, you might need to disable Hyper-V in the Windows Feature list.

We recommend you create a VM with the following attributes:

  • Memory Size: Set to 4096 MB (recommended)
  • Create a virtual hard disk with at least 10 GB (20 GB recommended)
  • Virtual hard disk file type: VDI (if you need to share it with other apps, use VHD)
  • (Optional) You can create a shared directory to copy block files or genesis files from the host computer to the VM. For details on how to create a shared directory, see “Share Folders” in the Oracle VirtualBox documentation.