You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/builders/node-operators/tutorials/mainnet.mdx
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,10 +28,10 @@ Below are suggested minimum hardware requirements for each type of node.
28
28
### SSD Capacity Requirements
29
29
30
30
Given the growing size of the blockchain state, choosing the right SSD size is important.
31
-
Below are the storage needs as of October 2024:
31
+
Below are the storage needs as of April 2024:
32
32
33
-
***Full Node:** The current size for a full node is approximately 420GB, with the data directory's capacity increasing by about 80GB every six months. Note that these figures are based on using the [Pebble database engine](../configuration/execution-config#dbengine) and the [path state scheme](../configuration/execution-config#statescheme).
34
-
***Archive Node:** The current size for an archive node is approximately 7TB, with the data directory's capacity increasing by about 3TB every six months.
33
+
***Full Node:** The snapshot size for a full node is approximately 1.6TB, with the data directory's capacity increasing by about 1TB every six months.
34
+
***Archive Node:** The snapshot size for an archive node is approximately 5TB, with the data directory's capacity increasing by about 3TB every six months.
35
35
36
36
Based on these trends, node operators should plan for future storage needs and choose SSDs that can handle these increasing requirements.
0 commit comments