blast-io/deployment

Unstable synchronization

johnny-vu opened this issue · 1 comments

I have problems with data synchronization, sometimes it stops for a few seconds then resumes

I am using: GCP 24 CPUs 24GB ram 1TB SSD, region us-central1-c & quicknode endpoint for L1

INFO [04-30|09:55:24.202] Chain head was updated                   number=2,830,554 hash=1be54f..882ee0 root=e3705b..5a4670 elapsed=2.487279ms
INFO [04-30|09:55:26.193] Imported new potential chain segment     number=2,830,555 hash=dcff87..2fb737 blocks=1 txs=10 mgas=1.116  elapsed=34.829ms   mgasps=32.035 snapdiffs=4.97MiB triedirty=0.00B
INFO [04-30|09:55:26.197] Chain head was updated                   number=2,830,555 hash=dcff87..2fb737 root=b8b8b2..9c0088 elapsed=2.62839ms
INFO [04-30|09:55:27.965] Imported new potential chain segment     number=2,830,556 hash=432b18..d3d77b blocks=1 txs=9  mgas=1.011  elapsed=44.978ms   mgasps=22.488 snapdiffs=4.97MiB triedirty=0.00B
INFO [04-30|09:55:27.969] Chain head was updated                   number=2,830,556 hash=432b18..d3d77b root=aecace..e8289e elapsed=2.733219ms
INFO [04-30|09:55:30.155] Imported new potential chain segment     number=2,830,557 hash=37d462..4ece06 blocks=1 txs=10 mgas=1.099  elapsed=134.560ms  mgasps=8.168  snapdiffs=996.83KiB triedirty=0.00B
INFO [04-30|09:55:30.172] Chain head was updated                   number=2,830,557 hash=37d462..4ece06 root=b1618d..e816d0 elapsed=3.560813ms
INFO [04-30|09:55:32.229] Imported new potential chain segment     number=2,830,558 hash=9a220c..11aa2a blocks=1 txs=9  mgas=1.256  elapsed=72.129ms   mgasps=17.414 snapdiffs=1002.00KiB triedirty=0.00B
INFO [04-30|09:55:32.233] Chain head was updated                   number=2,830,558 hash=9a220c..11aa2a root=43de1b..d5b7b2 elapsed=2.681605ms
INFO [04-30|09:55:34.587] Imported new potential chain segment     number=2,830,559 hash=062dbf..9dab38 blocks=1 txs=15 mgas=6.909  elapsed=255.446ms  mgasps=27.047 snapdiffs=1015.46KiB triedirty=0.00B
INFO [04-30|09:55:34.592] Chain head was updated                   number=2,830,559 hash=062dbf..9dab38 root=5a82f0..da6fe8 elapsed=3.339448ms
INFO [04-30|09:55:36.077] Imported new potential chain segment     number=2,830,560 hash=29c741..7ca79d blocks=1 txs=10 mgas=2.429  elapsed=56.997ms   mgasps=42.615 snapdiffs=1022.78KiB triedirty=0.00B
INFO [04-30|09:55:36.082] Chain head was updated                   number=2,830,560 hash=29c741..7ca79d root=788ac9..a613b0 elapsed=2.946537ms
INFO [04-30|09:55:37.950] Imported new potential chain segment     number=2,830,561 hash=5dcc4f..d3471c blocks=1 txs=6  mgas=0.818  elapsed=30.029ms   mgasps=27.237 snapdiffs=1.00MiB    triedirty=0.00B
INFO [04-30|09:55:37.954] Chain head was updated                   number=2,830,561 hash=5dcc4f..d3471c root=ae5a2c..ff13b9 elapsed=2.290746ms
INFO [04-30|09:55:40.506] Imported new potential chain segment     number=2,830,562 hash=a7c2fb..637a12 blocks=1 txs=7  mgas=1.838  elapsed=76.048ms   mgasps=24.166 snapdiffs=1.01MiB    triedirty=0.00B
INFO [04-30|09:55:40.510] Chain head was updated                   number=2,830,562 hash=a7c2fb..637a12 root=746e99..9f61f4 elapsed=2.798459ms
INFO [04-30|09:55:41.718] Imported new potential chain segment     number=2,830,563 hash=9ebc37..5bb307 blocks=1 txs=9  mgas=2.837  elapsed=62.493ms   mgasps=45.391 snapdiffs=1.02MiB    triedirty=0.00B
INFO [04-30|09:55:41.723] Chain head was updated                   number=2,830,563 hash=9ebc37..5bb307 root=76dee1..49b9cb elapsed=2.779387ms

Is there any way to make the synchronization more stable?

Have same issue