`monerod` sync performance

Cuprate / cuprate

Cuprate, an upcoming experimental, modern & secure monero node. Written in Rust

Other

112 stars 12 forks source link

`monerod` sync performance #195

Open hinto-janai opened 2 days ago

hinto-janai commented 2 days ago

What

This issue is a scratch pad for writing down monerod sync performance tests on a VPS.

VPS

Intel® Xeon® E5-2698v3 - 16 threads
32 GB memory
320 GB NVME SSD (unknown random/sequential read/write speeds)
10 Gb/s networking

`monerod.conf`

fast-block-sync=0 # Enabled/disabled depending on test

prune-blockchain=false
db-sync-mode=fastest:async
max-concurrency=0
prep-blocks-threads=16
log-level=1
no-zmq=true
disable-dns-checkpoints=true
enable-dns-blocklist=true
out-peers=512
in-peers=0
limit-rate-up=1280000
limit-rate-down=1280000

add-priority-node= # ... lots and lots of fast nodes

hinto-janai commented 2 days ago

2024-06-19 -> 2024-06-26

fast-block-sync was disabled
543600s wall clock uptime (6.29 days)
1192061s CPU time (2.19 CPU usage, 13% out of total)
3179629 height (chain-tip at the time) (5.84 blocks per second)
Peak memory usage was ~30GB, only around 5-10GB being required, the rest was cache

hinto-janai commented 2 days ago

2024-06-26

fast-block-sync was enabled
37692s wall clock uptime (~10 hours)
55877s CPU time (1.48 CPU usage, 9.3% out of total)
3109975 height (82.5 blocks per second)
Peak memory usage was ~23GB, only around ~8GB being required, the rest was cache

At the current rate of 5 blocks / second, it will take another 3.86 hours to finish to the previous height, 3179629, for a total of 51622s wall clock uptime or 14.33 hours.

2024-06-27

It took a total wall clock time of ~22 hours to reach the previous height (3179629).