Open directsyndikat opened 1 month ago
update:
It seems like its barely using any cores / memory. I tried adding the following flags without result: --db.read.concurrency=1024 --rpc.batch.concurrency=18
Polygon is very-very big.
Thanks, i just switched to Erigon3, this issue can be closed.
@AskAlexSharov Polygon is very-very big.
- or throw a lot of good hardware RAM, nvme, etc... and it still will take weeks.
- or switch to Erigon3 https://github.com/erigontech/erigon?tab=readme-ov-file#erigon3-users-guide
Im currently running Erigon3, upgraded my hardware. Running on 256GB RAM, 80 arm64 cores NVME but it seems its barely using resources. About 2% of total CPUis being used, it looks like its using 1 core and 24GB RAM being used while executing. Any idea how to use more of its CPU / RAM?
see screemshot here:
alpha3
soon). Please update and re-sync. SNAPSHOT_MADV_RND=false
may allow to use more read-IO. But probably you don't need.
Using: ./build/bin/erigon --chain=bor-mainnet --bor.heimdall=https://heimdall-api.polygon.technology/ --internalcl --prune=hrtc --torrent.download.rate=128mb
Expected behaviour: Prune till the latest 90.000 blocks.
Actual behaviour:
Questions: Does it require to execute all blocks till latest block and prune after? Is there a flag i can use to speed this up? Is this normal behaviour?
INFO[07-22|09:36:18.581] [7/15 Execution] Executed blocks number=15573548 blk/s=13.2 tx/s=2609.9 Mgas/s=267.1 gasState=1.30 batch=206.3MB alloc=7.3GB sys=12.6GB