Skip to content
This repository was archived by the owner on Apr 6, 2026. It is now read-only.

Update internal links to use relative paths #958

Merged
krofax merged 2 commits into from
Oct 7, 2024
Merged

Update internal links to use relative paths #958

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
38d49bf
Update SSD requirements and add config links
hash1go Oct 6, 2024
a149e8b
Revert SSD requirements
hash1go Oct 7, 2024
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
8 changes: 4 additions & 4 deletions pages/builders/node-operators/tutorials/mainnet.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -28,15 +28,15 @@ Below are suggested minimum hardware requirements for each type of node.
### SSD Capacity Requirements

Given the growing size of the blockchain state, choosing the right SSD size is important.
Below are the storage needs as of April 2024:
Below are the storage needs as of October 2024:

* **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.
* **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.
* **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).
* **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.
Comment thread
krofax marked this conversation as resolved.
Outdated

Based on these trends, node operators should plan for future storage needs and choose SSDs that can handle these increasing requirements.

<Callout type="info">
Geth supports a "freezer" feature to store older chain data on HDDs, saving SSD space. Configure this for OP Mainnet using the `--datadir.ancient` flag. See [Geth docs](https://geth.ethereum.org/docs/fundamentals/databases) and [OP docs](https://docs.optimism.io/builders/node-operators/configuration/execution-config#datadirancient) for details.
Geth supports a "freezer" feature to store older chain data on HDDs, saving SSD space. Configure this for OP Mainnet using the `--datadir.ancient` flag. See [Geth docs](https://geth.ethereum.org/docs/fundamentals/databases) and [OP docs](../configuration/execution-config#datadirancient) for details.
</Callout>

## Full Nodes
Expand Down