Skip to content

revising execution node hardware specs #1650

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vishalchangrani merged 1 commit into from
Feb 10, 2026
Merged

revising execution node hardware specs #1650

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 9 additions & 9 deletions docs/protocol/node-ops/node-operation/node-provisioning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,15 +9,15 @@ sidebar_position: 10

The hardware your Node will need varies depending on the role your Node will play in the Flow network. For an overview of the differences see the [Node Roles Overview](./node-roles.md).

| Node Type | CPU | Memory | Disk | Example GCP Instance | Example AWS Instance |
|:----------------:|:------------------------------:|:-------------------------:|:----------------:|:--------------------:|:--------------------:|
| **Collection** | 2 cores 🆕<br />(was 4 cores) | 8 GB 🆕<br />(was 32 GB) | 200 GB | n2-standard-2 | m5.large |
| **Consensus** | 2 cores | 8 GB 🆕<br />(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
| **Execution** | 128 cores | 864 GB | 9 TB<sup>1</sup> | n2-highmem-128 | |
| **Verification** | 2 cores | 8 GB 🆕<br />(was 16 GB) | 200 GB | n2-standard-2 | m5.large |
| **Access** | 8 cores 🆕<br />(was 16 cores) | 32 GB 🆕<br />(was 64 GB) | 750 GB | n2-standard-8 | m5.2xlarge |
| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |
| **EVM Gateway** | 2 cores | 32 GB | 30 GB | n2-highmem-4 | r6i.xlarge |
| Node Type | CPU | Memory | Disk | Example GCP Instance | Example AWS Instance |
|:----------------:|:--------------------------------:|:---------------------------:|:-----------------------------------:|:--------------------:|:--------------------:|
| **Collection** | 2 cores | 8 GB | 200 GB | n2-standard-2 | m5.large |
| **Consensus** | 2 cores | 8 GB | 200 GB | n2-standard-2 | m5.large |
| **Execution** | 80 cores 🆕<br />(was 128 cores) | 640 GB 🆕<br />(was 864 GB) | 6 TB<sup>1</sup> 🆕<br />(was 9 TB) | n2-highmem-80 | |
| **Verification** | 2 cores | 8 GB | 200 GB | n2-standard-2 | m5.large |
| **Access** | 8 cores | 32 GB | 750 GB | n2-standard-8 | m5.2xlarge |
| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |
| **EVM Gateway** | 2 cores | 32 GB | 30 GB | n2-highmem-4 | r6i.xlarge |

<sub>1: Recommended with maintenance see: [pruning chunk data pack](https://forum.flow.com/t/execution-node-upgrade-to-v0-31-15-and-managing-disk-space-usage/5167), 30 TB without maintenance.</sub>

Expand Down