From 8bc928a9c0fb7d8734c79477adb205e73100821d Mon Sep 17 00:00:00 2001 From: bgravenorst Date: Mon, 11 Aug 2025 08:07:23 +1000 Subject: [PATCH 1/3] Update system requirements. Signed-off-by: bgravenorst --- .../get-started/system-requirements.md | 21 ++++++++++++++++++- 1 file changed, 20 insertions(+), 1 deletion(-) diff --git a/docs/public-networks/get-started/system-requirements.md b/docs/public-networks/get-started/system-requirements.md index 41308515183..162d3a320bb 100644 --- a/docs/public-networks/get-started/system-requirements.md +++ b/docs/public-networks/get-started/system-requirements.md @@ -130,7 +130,26 @@ JVM memory requirements are highest when syncing, but will reduce after the node ## Disk space -[Fast synchronization](../reference/cli/options.md#sync-mode) with [pruning](../concepts/data-storage-formats.md) enabled requires approximately 750 GB of disk space. [Full synchronization](../reference/cli/options.md#sync-mode) requires approximately 3 TB. +The disk space required for syncing a Besu node depends on the +[sync mode](../concepts/node-sync.md#sync-modes) and +[data storage format](../concepts/data-storage-formats.md) used. +The following table summarizes approximate storage estimates and download times for each configuration. + +:::info +Besu uses snap sync with history pruning enabled by default for named networks such as Mainnet and +Sepolia. This configuration retains only block headers and the genesis block for +[pre-Merge](https://ethereum.org/en/roadmap/merge/) PoW history, significantly reducing disk usage. + +We recommend using snap sync instead of checkpoint sync because checkpoint sync will be deprecated +in the future. +::: + +| Storage format | Sync mode | World state sync time | Blockchain download time | Disk usage | +|----------------|---------------------------|-----------------------|--------------------------|------------| +| Bonsai | Snap (pruned) | ~3 hours | ~13 hours | 805 GB | +| Bonsai | Snap (unpruned) | ~3 hours | ~26 hours (est.) | 1164 GB | +| Bonsai | Checkpoint | ~3 hours | ~13 hours | >840 GB | +| Forest | Full | Weeks | Weeks | ~3 TB | ## Disk type From fd113d98afcde64a2c0dc8bed45072ca2f6247a9 Mon Sep 17 00:00:00 2001 From: bgravenorst Date: Mon, 11 Aug 2025 11:32:27 +1000 Subject: [PATCH 2/3] Remove stray quote. Signed-off-by: bgravenorst --- .../get-started/system-requirements.md | 22 +++++++++---------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/docs/public-networks/get-started/system-requirements.md b/docs/public-networks/get-started/system-requirements.md index 162d3a320bb..23e3143bfd7 100644 --- a/docs/public-networks/get-started/system-requirements.md +++ b/docs/public-networks/get-started/system-requirements.md @@ -52,17 +52,17 @@ docker image, or install the OpenJ9 JDK using the following steps: ```bash tar -xvf YOUR_J9_IMAGE.tar.gz ``` - + - - ```bash + + ```bash tar -xvf ibm-semeru-certified-jdk_x64_linux_21.0.3.0.tar.gz ``` - + 3. Move the binaries to `bin` directory: @@ -71,7 +71,7 @@ docker image, or install the OpenJ9 JDK using the following steps: ```bash sudo cp -r YOUR_IMAGE/ /usr/bin/ ``` - + @@ -81,7 +81,7 @@ docker image, or install the OpenJ9 JDK using the following steps: - + 4. Specify OpenJ9 for Java on your machine: @@ -91,17 +91,17 @@ docker image, or install the OpenJ9 JDK using the following steps: sudo update-alternatives --install "/usr/bin/java" "java" "/usr/bin/YOUR_IMAGE" 1 sudo update-alternatives --config java (and choose OpenJ9) ``` - + ```bash sudo update-alternatives --install "/usr/bin/java" "java" "/usr/bin/jdk-21.0.3+9/bin/java" ``` - + - + Change your `JAVA_HOME` to OpenJ9 (if using the JDK implementation), where `jdk-install-dir` is the installation location you specified: @@ -109,7 +109,7 @@ docker image, or install the OpenJ9 JDK using the following steps: ```bash - export JAVA_HOME=jdk-install-dir` + export JAVA_HOME=jdk-install-dir ``` @@ -118,7 +118,7 @@ docker image, or install the OpenJ9 JDK using the following steps: ```bash export JAVA_HOME=/usr/bin/jdk-21.0.3+9 ``` - + From 27f8d03ce06f5b1f95bee0656b4e6bb3de1fb845 Mon Sep 17 00:00:00 2001 From: Byron Gravenorst <50852695+bgravenorst@users.noreply.github.com> Date: Tue, 12 Aug 2025 08:55:01 +1000 Subject: [PATCH 3/3] Update docs/public-networks/get-started/system-requirements.md Co-authored-by: Alexandra Carrillo <12214231+alexandratran@users.noreply.github.com> Signed-off-by: Byron Gravenorst <50852695+bgravenorst@users.noreply.github.com> --- docs/public-networks/get-started/system-requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/public-networks/get-started/system-requirements.md b/docs/public-networks/get-started/system-requirements.md index 23e3143bfd7..a8abf6c9b4b 100644 --- a/docs/public-networks/get-started/system-requirements.md +++ b/docs/public-networks/get-started/system-requirements.md @@ -138,7 +138,7 @@ The following table summarizes approximate storage estimates and download times :::info Besu uses snap sync with history pruning enabled by default for named networks such as Mainnet and Sepolia. This configuration retains only block headers and the genesis block for -[pre-Merge](https://ethereum.org/en/roadmap/merge/) PoW history, significantly reducing disk usage. +[pre-merge](https://ethereum.org/en/roadmap/merge/) PoW history, significantly reducing disk usage. We recommend using snap sync instead of checkpoint sync because checkpoint sync will be deprecated in the future.