Storage.
12 stories
Apothem datadir size by xOne client: measured after snap sync
How big an xOne Apothem datadir is after snap sync, per client: 13 to 72 GB as recorded in issue 149, a fresh byte count, growth over eight hours, and why.
How to plan disk space for an XDC node with xOne
Plan disk for an XDC node with xOne: the node's 2%, 3% and 1% free-space lines, the 15% alert, datadir sizes per sync mode, segment files and MDBX limits.
Disk watermarks and block sealing: why a full disk stops xOne
Why a low disk stops block sealing in xOne on XDC: one gate for import and producer, the NoSpace second line, and what the four clients do at the exit line.
Four XDC clients on one host: load and disk records
What xOne recorded with four XDC clients on one shared host: the 27-minute Python seat outage, load averages, disk lines and the memory cap, with sources.
Inside xOneC: MDBX and the producer path on XDC
Follow one block through xOneC, the C++ XDC client, from import to the libmdbx commit, then one sealed block from the leader turn to broadcast, with file:line.
Inside xOnePy: SQLite WAL and the event loop on XDC
How xOnePy, the Python XDC client, sets SQLite WAL, owns BEGIN and COMMIT, groups commits, and keeps its asyncio loop free, with the numbers its repo records.
Inside xOneTS: SQLite storage and dense sync on XDC
How xOneTS keeps XDC chain data in bun:sqlite and segment files, how group commit and the hashed-key migration work, and what the dense-sync fix changed.
The xone db toolkit: inspect, check, repair and compare an XDC node's database
Every xone db subcommand in xOneRS, grouped by job: what each reads or writes, which ones are safe beside a running node, and which need the node stopped.
XDC node hardware and disk requirements for xOne
XDC node hardware requirements for xOne: no CPU or RAM sizing is published. Read the enforced limits, disk watermarks, and the memory and disk use measured.
History retention in xOne: pruning bodies, receipts, logs and state, and backfill
The xOneRS --history flags: how long a node keeps bodies, receipts, logs, state and preimages, how to prune a stopped datadir, and backfill after snap sync.
Smaller and safer xOne datadirs: zstd segments, compact receipts and a staging volume
Five xOneRS storage changes: zstd history segments, receipts without stored blooms, size-capped segment files, a staging volume and a resize-aware disk guard.
How xOne stores XDC chain data: engines and datadir
How xOne stores XDC chain data in its four clients: the database engine of each, the datadir files, segment publication, crash-safe commits and datadir sizes.
Edit this page on GitHub opens the page source (app/blog/tags/[tag]/page.jsx). GitHub may ask you to sign in. Report a correction opens a prefilled GitHub issue for this page.