docs(hardware): freeze v3.4 disk sizes as static values - #22583
Closed
bloxster wants to merge 1 commit into
Closed
Conversation
The v3.4 versioned hardware-requirements page imported the shared, live src/data/disk-sizes.json, so it rendered whatever the deploy branch (release/3.5) currently holds (the Sep 2025 values) instead of the values measured for the 3.4 release. Freeze the v3.4 "Current Disk Usage" column to the 3.4-era measured values (each obtained by syncing a node per prune mode) and drop the now-unused JSON import, matching how Polygon is already frozen on this page. Versioned docs are frozen snapshots, so static values are the correct representation. mainnet: archive 2.03 TB, full 1.2 TB, minimal 360 GB gnosis: archive 605 GB, full 645 GB, minimal 186 GB The current (v3.5) page keeps reading the live JSON and will be updated with freshly measured 3.5 values separately. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
bloxster
force-pushed
the
docs/restore-disk-sizes-jun2026
branch
from
July 19, 2026 16:15
eda7c98 to
009b709
Compare
bloxster
changed the title
Collaborator
Author
|
Superseded by #22596. That PR makes disk sizes static site-wide (Option C from the adversarial review) and folds in this v3.4 freeze as part of a self-consistent change (static current page + static versioned pages + fail-closed CI guard). |
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
1 participant
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
Freezes the v3.4 versioned hardware-requirements page to static, 3.4-era measured disk sizes, and removes its
disk-sizes.jsonimport.Why
The v3.4 versioned page imported the shared, live
@site/src/data/disk-sizes.json. Since the site deploys fromrelease/3.5, that file holds the current (Sep 2025) values — so/v3.4/get-started/hardware-requirementsrendered those instead of the values measured for the 3.4 release. Versioned docs are frozen snapshots, so their disk sizes should be static (the Polygon rows on this page are already hardcoded for the same reason).Values frozen (measured by syncing a node per prune mode)
Scope / follow-ups
versioned_docs/version-v3.4/.... The shareddisk-sizes.jsonis untouched.Note: v3.5 full (~421 GB) is genuinely smaller than v3.4 full (1.2 TB) — a real version-over-version reduction, which is why each version keeps its own measured numbers.
Verification
python3 docs/site/scripts/generate-llms.py --check— OK (4 llms files, 74 pages).npm run build— production build succeeds.🤖 Generated with Claude Code