docs(hardware): refresh v3.5 measured disk sizes (mainnet + gnosis) - #22640
Merged
Conversation
Updates disk-sizes.json (and the rendered hardware-requirements markers) with fresh v3.5.2 default-config measurements: mainnet: archive 2.03 TB, full 419.04 GB, minimal 378.97 GB (2026-07-19) gnosis: archive 673.59 GB, full 220.10 GB, minimal 204.45 GB (2026-07-21) Previous values were manual estimates from 2025-09. All measured with `du -sb` on fully-synced nodes running default config (only --prune.mode set), so receipts follow the release/3.5 default (kept for full/minimal; archive keeps the full receipt domain as part of its history). llms artifacts regenerated.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates Erigon documentation disk-usage figures for v3.5 using freshly measured du -sb results (mainnet + gnosis), keeping the static-marker rendering workflow intact (JSON as source-of-record → rendered MDX + LLM export text).
Changes:
- Refreshed mainnet and gnosis “Current Disk Usage” values and measurement dates in
disk-sizes.json. - Regenerated the hardware requirements MDX static markers from the updated JSON.
- Updated the LLM-exported
llms-full.txtcopies to reflect the new numbers/dates.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| llms-full.txt | Updates the exported disk-usage tables/dates to match the new measurements. |
| docs/site/static/llms-full.txt | Keeps the site’s static LLM export in sync with the updated disk-usage figures. |
| docs/site/src/data/disk-sizes.json | Source-of-record update: new bytes/display values + measured_at dates for mainnet/gnosis. |
| docs/site/docs/get-started/hardware-requirements.mdx | Regenerated static marker values/dates so the rendered docs reflect the updated JSON. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
AskAlexSharov
approved these changes
Jul 22, 2026
This was referenced Jul 28, 2026
Merged
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
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.
What
Refreshes the "Current Disk Usage" figures on the Hardware Requirements page with fresh v3.5.2, default-config measurements. Previous values were manual estimates from 2025-09.
How measured
du -sbon fully-synced nodes running v3.5.2 with default config (only--prune.modeset — no--persist.receiptsoverride), so receipts follow the default: kept for full/minimal; archive carries the full receipt domain as part of its history.disk-sizes.json).disk-sizes.jsonupdated (source of record);hardware-requirements.mdxregenerated from it viascripts/render-disk-sizes.py(static markers);render --checkand the llms--checkboth pass.Notes
sourceismanualfor all rows this cycle (hand-measured). CI (update-disk-sizes.yml) will resume writingfull/minimalascion the next sync-from-scratch run.