Data storage formats
Besu offers two formats for storing the world state, Forest of Tries and Bonsai Tries.
Forest of Tries
Forest of Tries, also called forest mode, is the default storage format.
In forest mode, each node in the trie is saved in a key-value store by hash. For each block, the world state is updated with new nodes, leaf nodes, and a new state root. Old leaf nodes remain in the underlying data store. Data is accessed and stored by hash, which increases the size of the database and increases the resources and time needed to access account data.
Pruning reduces the storage required by removing state trie nodes unreachable from recent blocks.
Pruning is disabled by default, and can be enabled with the
--pruning-enabled command line option.
Using pruning with private transactions\ isn’t supported.
Pruning might increase block import times, but it doesn’t affect the ability of nodes to stay in sync.
Pruning is being deprecated for Bonsai Tries and is currently not being updated.
Bonsai Tries is a data storage layout policy designed to reduce storage requirements and increase read performance.
Bonsai stores leaf values in a trie log, separate from the branches of the trie. Bonsai stores nodes by the location of the node instead of the hash of the node. Bonsai can access the leaf from the underlying storage directly using the account key. This greatly reduces the disk space needed for storage and allows for less resource-demanding and faster read performance. Bonsai inherently prunes orphaned nodes and old branches.
To run a node with Bonsai Tries data storage format, use the command line option
Forest of Tries vs. Bonsai Tries
Forest mode uses significantly more memory than Bonsai. With an archive node, forest mode uses an estimated 12 TB of storage, while Bonsai uses an estimated 1100 GB of storage. With a full node, forest mode uses an estimated 750 GB of storage, while Bonsai uses an estimated 650 GB of storage.
Forest mode must go through all the branches by hash to read a leaf value. Bonsai can access the leaf from the underlying storage directly using the account key. Bonsai will generally read faster than forest mode, particularly if the blocks are more recent.
However, Bonsai becomes increasingly more resource-intensive the further in history you try to read data. To prevent this, you can limit how far Bonsai looks back while reconstructing data. The default limit Bonsai looks back is 512. To change the parameter, use the
--bonsai-maximum-back-layers-to-load doesn’t affect the size of the database being stored, only how far back to load. This means there is no “safe minimum” value to use with this option.
The following table shows the ways you can sync a full node with the different data storage formats using fast and snap sync.
|Data storage format||Sync mode||Storage estimate||Can other nodes sync to your node?|
|Bonsai||Snap||650 GB||To be implemented|
|Forest||Snap||750 GB||To be implemented|
We recommend using snap sync with Bonsai for the fastest sync and lowest storage requirements.