How to reduce database size
Description of all possible options, their pros and cons
The Nethermind database can experience substantial growth over time, starting from an initial size of approximately 650 GB. As a result, many node-setups are configured to run on 1TB disks. However, even with the application of settings designed to slow the growth rate, these disks may eventually run out of free space.
Current options to reduce db size are:
The table below presents a short comparison of these methods including possible fine-tuning of each method. Data was fetched from a node running on a machine with the below specifications: Node Version: 1.18.0 Consensus Client: Lighthouse CPU: AMD EPYC 7713 64-Core Processor (16 cores allocated for this VM) RAM: 64GB Disk Size: 1.2 TB IOPS of the disk*: 70,000 - 80,000 IOPS (results vary in this range)
Command used for testing IOPS of disk:
fio --randrepeat=1 --ioengine=libaio --direct=1 --gtod_reduce=1 --name=test --filename=test --bs=4k --iodepth=64 --size=4G --readwrite=randrw