docs(installation): mention blob storage CPU and disk impact#9320
Open
0xghost42 wants to merge 1 commit into
Open
docs(installation): mention blob storage CPU and disk impact#93200xghost42 wants to merge 1 commit into
0xghost42 wants to merge 1 commit into
Conversation
Adds a Blob storage considerations subsection that briefly mentions the additional CPU and storage requirements for retaining blob history or running as a supernode, and links forward to the Blobs page for full details. Refreshes the trailing 'Last update' line. Closes sigp#9213
|
|
chong-he
reviewed
May 20, 2026
Member
chong-he
left a comment
chong-he
left a comment
There was a problem hiding this comment.
Spelling check is failing. You can use terabytes instead of TiB
|
|
||
| The system requirements above cover a default beacon node with a modest validator workload. Running with full blob retention — and especially as a [supernode archive](./advanced_blobs.md) — significantly increases both CPU and storage demands. | ||
|
|
||
| If you intend to store blob history beyond the rolling retention window, or if you plan to run with `--supernode` or `--semi-supernode`, plan for: |
Member
There was a problem hiding this comment.
I think the proper term is "data availability window", we can say this and then add in a bracket (18 days) for clarity
|
|
||
| If you intend to store blob history beyond the rolling retention window, or if you plan to run with `--supernode` or `--semi-supernode`, plan for: | ||
|
|
||
| - **CPU:** a faster single-core clock (around 5 GHz) helps keep up with blob verification under load. |
Member
There was a problem hiding this comment.
I am not sure if it is a good idea to put 5 GHz here.
From the data here: https://browser.geekbench.com/processor-benchmarks, the base speed is all < 5 GHz. While it can be overclocked, but I don't think staking operators will tend to do this.
For simplicity we can just remove the number here
chong-he
added
waiting-on-author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The installation guide currently lists system requirements that pre-date blob storage and doesn't surface the additional cost of retaining blob history (or running as a supernode). New operators who follow only `installation.md` can end up under-provisioned on either CPU or disk.
This change adds a short "Blob storage considerations" subsection that:
Also refreshes the trailing `Last update` line.
Closes #9213
Additional Info
Documentation-only change; no code, CLI, or behavior changes. Flag names cross-checked against `beacon_node/src/cli.rs` (`--supernode` is the canonical name; `--subscribe-all-data-column-subnets` is an alias) and `book/src/advanced_blobs.md`.