bsc
bsc copied to clipboard
bnb-chain
Chaindata sizes for archive nodes (active vs ancient)
I apologize for the new Issue, as this is slightly related to several other open threads, but wanted to have a direct answer under the specific parameters.
Could someone provide the current approximate size of chaindata under an archive node, but separately provide the size of chaindata/ancient? I am trying to determine whether a dedicated 2 TB NVMe drive is sufficient for operation if --datadir.ancient is set to a separate volume.
Thank you!
Maybe it's a config difference, but my archive nodes don't have a separate ancient folder. Total size is currently 4.0 TiB (meaning a 4TB drive wouldn't cut it by approx 0.5 TiB).
@koen84 - From the root of your node directory, you don't have geth/chaindata/ancient? It's certainly possible I'm misunderstanding how archive nodes work, but would have thought it would still move some stuff out..
@DefiDebauchery i went to check back, maybe i missed it before amidst the massive amount of output in the chaindata, but there's indeed an ancient folder : 107 GiB on both my archive nodes.
So out of 4TB, only 107G is staged in the ancient folder? That's disappointing (and quite different from Ethereum's description of the ancient folder - dubbed the 'Freezer' in this post); I was expecting much more. I just bought a 4TB SSD hoping ancient could be offset.. I couldn't even use it for the full data if it requires more than 4TB. How the heck are folks even running archive nodes at this point if IOPS is the bottleneck?
Anyway, thank you for looking into that for me.
It's growing pretty fast, it increased by almost 1TB during last 14 days
RAID10 NVMe with 4x 4TB NVMe and it definitely grows like crazy. I started at 0.9TiB something 2-3 months ago.
I don't know if the ancient blocks can be tweaked ?