Skip to content

Commit 91dbe02

Browse files
authored
Update Bonsai size and behavior (#1005)
* Update Bonsai size and behavior Signed-off-by: Roland Tyler <roland.tyler@consensys.net> * Update Bonsai size and behavior Signed-off-by: Roland Tyler <roland.tyler@consensys.net> * fix Signed-off-by: Roland Tyler <roland.tyler@consensys.net>
1 parent e6328bb commit 91dbe02

File tree

1 file changed

+6
-1
lines changed

1 file changed

+6
-1
lines changed

docs/Concepts/Data-Storage-Formats.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ To run a node with Bonsai Tries data storage format, use the command line option
3636
### Storage requirements
3737

3838
Forest mode uses significantly more memory than Bonsai. With full archives, forest mode uses an estimated 12 TB of storage,
39-
while Bonsai with full archives uses an estimated 800 GB of storage.
39+
while Bonsai with full archives uses an estimated 1100 GB of storage.
4040

4141
### Accessing data
4242

@@ -49,6 +49,11 @@ To prevent this, you can limit how far Bonsai looks back while reconstructing da
4949
The default limit Bonsai looks back is 512. To change the parameter, use the
5050
[`--bonsai-maximum-back-layers-to-load`](../Reference/CLI/CLI-Syntax.md#bonsai-maximum-back-layers-to-load) option.
5151

52+
!!! note
53+
54+
Using `--bonsai-maximum-back-layers-to-load` doesn't affect the size of the database being stored, only how far back to load.
55+
This means there is no "safe minimum" value to use with this option.
56+
5257
### Fast syncing nodes
5358

5459
With forest mode, your node can use [fast synchronization](Node-Types.md#run-a-full-node) as normal.

0 commit comments

Comments
 (0)