readme: refresh disk sizes from 3.6 archive nodes, drop polygon - #22866
Open
awskii wants to merge 2 commits into
Open
readme: refresh disk sizes from 3.6 archive nodes, drop polygon#22866awskii wants to merge 2 commits into
awskii wants to merge 2 commits into
Conversation
Sizes were 1-2 years stale (mainnet/gnosis May 2025, polygon April 2024, datadir breakdown Nov 2024) and the bor-mainnet du block was never real output - it prints /erigon-data rows for a du run on /erigon/snapshots/*. Measured on the snapshotter-bm-v36-* archive nodes. Optional data that is off by default (receipts, commitment history, caplin archive) is broken out separately instead of being folded into the totals. Polygon is dropped: the final release series that officially supports it is 3.1.*, per docs/site/docs/fundamentals/supported-networks.md. Also fixed in the touched paragraphs: two dead #cloud-network-drives self-anchors, the domain count (4 -> 6), the chaindata size claim, and the renamed --caplin.archive flag.
The breakdown covered only eth-mainnet and gnosis. Same five chains as the docs Database page now, in the same units, so the two agree digit-for-digit.
awskii
enabled auto-merge
July 29, 2026 15:13
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.
Disk sizes in the README were 1-2 years stale: mainnet/gnosis dated May 2025, polygon April 2024, and the datadir breakdown November 2024. The bor-mainnet
dublock was never real output either — it prints/erigon-data/...rows for a command run on/erigon/snapshots/*.Numbers are measured on the
snapshotter-bm-v36-*archive nodes. Those boxes run with receipts, commitment history and Caplin archive enabled, so the per-component data is split: the totals are a default--prune.mode=archivenode, and the optional data is listed separately with the flag that turns it on.Polygon is dropped throughout. Per
docs/site/docs/fundamentals/supported-networks.md, the final release series that officially supports it is 3.1.*.Changes
dublocks replaced with a per-subdir table across the same five chains, plus a table of what receipts / commitment history / Caplin archive each add--chain=bor-mainnet/--chain=amoy, and the "experimental for Polygon" block-production clause#cloud-network-drivesself-anchors (the section moved to the docs site in Created dedicated folder for help section #17896), domain count 4 -> 6 (db/kv/tables.go:719-725), thechaindata < 15gbclaim, and the renamed--caplin.archiveflag (now--caplin.{blocks,blobs,states}-archive)Figures are byte-exact and use the same units as the docs Database page, so the two agree digit-for-digit.
erigon snapshots duindependently reproduces the per-category totals.Notes
Pairs with #22867, which refreshes the same numbers on the docs site. Sync Times is untouched — no fresh measurement, and it has not been updated since January 2025.