-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
op-reth Base Mainnet sync very slowly #413
Comments
Hi @0xStrawberlin |
i am using a geth node, and i have added the full node snapshot but after that, i was about 20k blocks behind so i waited couple of hours. but i realised it is still syncing very slow. Average sync speed: 1.7750 blocks per second
what can i do to debug the speed? i am on ubuntu 24.04, 16 core xeon 6th gen CPU with 64 GB ram and 2TB nvme disk i am using chainstack as my L1 becon node which have a throughput of 25 api calls per sec Thanks |
I try to run a full base mainnet node with op-reth and op-node. But it syncs very slowly. It took about 15 hours to run and only reached 400,000 blocks. Can anyone provide the full node snapshot ? or Can I sync from latest block instead of genius block (Block 0). Thank!
Here are my executed scripts:
./bin/op-node \ --network="base-mainnet" \ --l1=wss://eth.merkle.io \ --l2=http://localhost:9551 \ --l2.jwt-secret=/Volumes/Tiplus/reth_data/base_reth_jwt/jwt.hex \ --rpc.addr=0.0.0.0 \ --rpc.port=7000 \ --l1.beacon=https://ethereum-beacon-api.publicnode.com --l1.trustrpc --syncmode=execution-layer --l2.enginekind=reth --override.holocene 2736445601 op-reth node \ --full \ --chain base \ --rollup.sequencer-http https://mainnet-sequencer.base.org \ --http \ --ws \ --authrpc.port 9551 \ --authrpc.jwtsecret /Volumes/Tiplus/reth_data/base_reth_jwt/jwt.hex \ --datadir /Volumes/Tiplus/reth_data/base_reth_data
The text was updated successfully, but these errors were encountered: