rippled icon indicating copy to clipboard operation
rippled copied to clipboard

Why is the synchronization of previous XRP blocks so slow?????

Open fancydd opened this issue 10 months ago • 3 comments

Why is the synchronization of previous XRP blocks so slow? I’ve been running it for 4 days, and it has only synced data from the past month.

fancydd avatar Mar 05 '25 04:03 fancydd

Hello. To double check: is your intention to run the node in a Historical mode? When using the node in validation mode, it should take ~15 when starting from scratch to get into the state where the node is fully synced with recent data and ready to start proposing new ledgers.

vlntb avatar Mar 06 '25 12:03 vlntb

Why is the synchronization of previous XRP blocks so slow? I’ve been running it for 4 days, and it has only synced data from the past month.

The short explanation is:

  1. Fetching history is the lowest priority operation in rippled.
  2. Providing history is burdensome to the other nodes your node is connected to (peers). If your node requests too much data too quickly, your peers may get overloaded and drop you. To avoid that, rippled sends historical data requests slowly. You might be able to get more data more quickly by allowing more connections in your configuration.

Frankly, getting a month's ledgers in only 4 days isn't bad.

ximinez avatar Mar 11 '25 15:03 ximinez