erigontech / erigon

Ethereum implementation on the efficiency frontier https://erigon.gitbook.io
GNU Lesser General Public License v3.0
3.09k stars 1.08k forks source link

execution 7/15 slow #11272

Open directsyndikat opened 1 month ago

directsyndikat commented 1 month ago

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:

Screenshot 2024-07-22 at 09 35 21

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

directsyndikat commented 1 month ago

update:

Screenshot 2024-07-22 at 11 43 07

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

AskAlexSharov commented 1 month ago

Polygon is very-very big.

directsyndikat commented 1 month ago

Thanks, i just switched to Erigon3, this issue can be closed.

directsyndikat commented 1 month ago

@AskAlexSharov Polygon is very-very big.

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?

directsyndikat commented 1 month ago

see screemshot here:

Screenshot 2024-07-27 at 00 01 53
AskAlexSharov commented 4 days ago
  1. We released new files of E3 polygon (will do alpha3 soon). Please update and re-sync.
  2. It using all RAM: https://github.com/erigontech/erigon?tab=readme-ov-file#htop-shows-incorrect-memory-usage
  3. SNAPSHOT_MADV_RND=false may allow to use more read-IO. But probably you don't need.
  4. Let it sync 1 day - if will have problems - then show logs.