* EBS volumes are significantly slower than physical SSDs attached to the VM.
#ETHEREUM GETH INSTALL ARCHIVE#
We’ve run an archive sync benchmark on two m5.2xlarge AWS EC2 instances (8 core, 32 GiB RAM, 3TiB EBS SSD) with -cache=4096 -syncmode=full -gcmode=archive. The reason for the higher disk IO is due to using less memory for caching, having to push more aggressively to disk. *Whilst the performance is similar, we’ve achieved that while reducing the memory use by about 1/3rd and completely removing spurious memory peaks (Shanghai DoS).
#ETHEREUM GETH INSTALL FULL#
We’ve run a full sync benchmark on two i3.2xlarge AWS EC2 instances (8 core, 61 GiB RAM, 1.9 TiB NVMe SSD) with -cache=4096 -maxpeers=50 -syncmode=full. We’ve run a fast sync benchmark on two i3.2xlarge AWS EC2 instances (8 core, 61 GiB RAM, 1.9 TiB NVMe SSD) with -cache=4096 -maxpeers=50 (defaults on v1.9.0) on the 25th of April. This work was mostly done by Péter Szilágyi. By temporarily allocating pruning caches to fast sync blooms, we’ve been able to short circuit most data accesses in-memory.
This resulted in stabilizing Geth’s memory usage even during the import of the Shanghai DoS blocks and speeding up overall block processing by concurrent heuristic state prefetching.