docs(installation): mention blob storage requirements#9537
Open
daixihegu wants to merge 1 commit into
Open
Conversation
Signed-off-by: daixihegu <daixihegu@163.com>
|
|
chong-he
reviewed
Jun 26, 2026
chong-he
left a comment
chong-he
left a comment
Member
There was a problem hiding this comment.
Spell check is failing. Maybe we don't have to add TiB to the wordlist, we can spell the word out
| Last update: April 2023 | ||
| ### Blob and data column storage | ||
|
|
||
| The storage recommendation above assumes default blob pruning. Operators who retain blob history, run a `--semi-supernode` or `--supernode`, or disable blob/data column pruning can require substantially more disk space, potentially multiple TiB of fast SSD storage on top of the standard beacon node and execution client databases. These modes can also benefit from strong single-core CPU performance, with around 5 GHz suggested for demanding supernode/archive configurations. See [Blobs](./advanced_blobs.md) for the current retention modes and detailed trade-offs. |
Member
There was a problem hiding this comment.
who retain blob history, run a , or disable blob/data column pruning
retain blob history and disable blob/data column pruning mean the same thing. So we can just say:
who retain blob history via `--prune-blobs false` or run a `--semi-supernode` or `--supernode`
| Last update: April 2023 | ||
| ### Blob and data column storage | ||
|
|
||
| The storage recommendation above assumes default blob pruning. Operators who retain blob history, run a `--semi-supernode` or `--supernode`, or disable blob/data column pruning can require substantially more disk space, potentially multiple TiB of fast SSD storage on top of the standard beacon node and execution client databases. These modes can also benefit from strong single-core CPU performance, with around 5 GHz suggested for demanding supernode/archive configurations. See [Blobs](./advanced_blobs.md) for the current retention modes and detailed trade-offs. |
Member
There was a problem hiding this comment.
I left a comment here in a previous PR about mentioning specifically 5GHz here:
https://github.com/sigp/lighthouse/pull/9320/changes
Maybe we want to tune the wording a bit
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.
Issue Addressed
Closes #9213.
Proposed Changes
Adds a short note to the installation system requirements about blob and data column storage.
Additional Info
The existing requirements assume default blob pruning. This update calls out that retaining blob history, running
--semi-supernodeor--supernode, or disabling blob/data column pruning can require substantially more fast SSD storage and stronger single-core CPU performance. It also links readers to the existing Blobs page for the detailed trade-offs.