Open lcgogo opened 3 years ago
I have tried openeth-3.0.1 and peth-2.5.13-stable, the sync rates are nearly same.
`# docker logs --tail 5 peth-2.5.13-stable 2020-09-11 14:55:40 UTC Syncing #2701197 0xf611…07b1 1.00 blk/s 2.6 tx/s 0.6 Mgas/s 0+ 7077 Qed #2708278 41/50 peers 5 MiB chain 18 MiB db 46 MiB queue 63 MiB sync RPC: 0 conn, 0 req/s, 19 µs 2020-09-11 14:55:45 UTC Syncing #2701197 0xf611…07b1 0.00 blk/s 0.0 tx/s 0.0 Mgas/s 0+ 7077 Qed #2708278 41/50 peers 5 MiB chain 18 MiB db 46 MiB queue 63 MiB sync RPC: 0 conn, 0 req/s, 19 µs 2020-09-11 14:55:50 UTC Syncing #2701199 0xb6c6…2620 0.40 blk/s 4.2 tx/s 0.6 Mgas/s 0+ 7077 Qed #2708278 41/50 peers 5 MiB chain 18 MiB db 46 MiB queue 63 MiB sync RPC: 0 conn, 0 req/s, 19 µs 2020-09-11 14:55:55 UTC Syncing #2701200 0xda7f…b8ab 0.20 blk/s 1.6 tx/s 0.5 Mgas/s 0+ 7077 Qed #2708278 41/50 peers 5 MiB chain 18 MiB db 46 MiB queue 63 MiB sync RPC: 0 conn, 0 req/s, 19 µs 2020-09-11 14:56:00 UTC Syncing #2701200 0xda7f…b8ab 0.00 blk/s 0.0 tx/s 0.0 Mgas/s 0+ 7077 Qed #2708278 41/50 peers 5 MiB chain 18 MiB db 46 MiB queue 63 MiB sync RPC: 0 conn, 0 req/s, 19 µs
UID PID PPID C STIME TTY TIME CMD nobody 18735 18707 99 Sep10 ? 1-16:10:47 /bin/parity -d=/data/peth --jsonrpc-interface=all --pruning=archive --pruning-history=6000 --tracing on --tx-queue-mem-limit=10 --tx-queue-size=16384 --tx-queue-per-sender=200 --jsonrpc-server-threads=100 --max-peers=100 --min-peers=50 --bootnodes enode://68f46370191198b71a1595dd453c489bbfe28036a9951fc0397fabd1b77462930b3c5a5359b20e99677855939be47b39fc8edcf1e9ff2522a922b86d233bf2df@144.217.153.76:30303,enode://ffed6382e05ee42854d862f08e4e39b8452c50a5a5d399072c40f9a0b2d4ad34b0eb5312455ad8bcf0dcb4ce969dc89a9a9fd00183eaf8abf46bbcc59dc6e9d5@51.195.3.238:30303
d92aec200a0d parity/parity:v2.5.13-stable "/bin/parity -d=/dat…" 34 hours ago Up 34 hours 5001/tcp, 8080/tcp, 8082-8083/tcp, 8180/tcp, 8546/tcp, 30303/tcp, 30303/udp, 0.0.0.0:8545->8545/tcp peth-2.5.13-stable`
Before filing a new issue, please provide the following information.
If you think that your issue is an exploitable security vulnerability, please mail your bugreport to security@parity.io instead; your submission might be eligible for our Bug Bounty. You can find mode info on the reporting process in SECURITY.md
Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue.
I started a server sync from 0 by archive mode days before. However, may need more than 700 days to catch up current height according to current rate of blk/s.
docker top peth-3.0.1
UID PID PPID C STIME TTY TIME CMD nobody 1646 1604 97 Sep09 ? 2-06:20:47 ./openethereum -d=/data/peth --jsonrpc-interface=all --pruning=archive --pruning-history=6000 --tracing on --tx-queue-mem-limit=10 --tx-queue-size=16384 --tx-queue-per-sender=200 --jsonrpc-server-threads=100
docker ps | grep peth
7317d678b7eb openethereum/openethereum:v3.0.1 "./openethereum -d=/…" 2 days ago Up 2 days 8080/tcp, 8180/tcp, 0.0.0.0:8545->8545/tcp peth-3.0.1
docker logs -f --tail 20 peth-3.0.1
2020-09-11 14:48:07 UTC Syncing #2704312 0xfea3…6b84 0.20 blk/s 1.2 tx/s 0.3 Mgas/s 0+ 5848 Qed #2710172 25/25 peers 6 MiB chain 18 MiB db 46 MiB queue 105 MiB sync RPC: 0 conn, 0 req/s, 16 µs 2020-09-11 14:48:12 UTC Syncing #2704316 0xeec6…8db0 0.80 blk/s 2.6 tx/s 0.2 Mgas/s 0+ 5848 Qed #2710172 25/25 peers 6 MiB chain 18 MiB db 46 MiB queue 105 MiB sync RPC: 0 conn, 0 req/s, 16 µs 2020-09-11 14:48:17 UTC Syncing #2704317 0x8d1a…7645 0.20 blk/s 2.2 tx/s 0.4 Mgas/s 0+ 5848 Qed #2710172 25/25 peers 6 MiB chain 18 MiB db 46 MiB queue 105 MiB sync RPC: 0 conn, 0 req/s, 16 µs 2020-09-11 14:48:22 UTC Syncing #2704322 0x2cec…d4a3 1.00 blk/s 2.8 tx/s 0.2 Mgas/s 0+ 5848 Qed #2710172 25/25 peers 6 MiB chain 18 MiB db 46 MiB queue 105 MiB sync RPC: 0 conn, 0 req/s, 16 µs 2020-09-11 14:48:27 UTC Syncing #2704323 0x582f…cfad 0.20 blk/s 1.0 tx/s 0.4 Mgas/s 0+ 5848 Qed #2710172 25/25 peers 6 MiB chain 18 MiB db 46 MiB queue 105 MiB sync RPC: 0 conn, 0 req/s, 16 µs 2020-09-11 14:48:32 UTC Syncing #2704323 0x582f…cfad 0.00 blk/s 0.0 tx/s 0.0 Mgas/s 0+ 5848 Qed #2