0

I've set up a full Parity Ethereum node connected to the main network on a server with 2TB SSD, 4 CPUs and 8GB memory.

I've set the pruning mode to archive since my application does a lot of state querying, so the thinking was that the fast mode would not be suitable for this usecase.

The syncing from the genesis block to block 4,500,000 took about 2 days, which wasn't too bad. That said, the next 1,100,000 blocks from 4,500,000 to 5,600,000 took about 3 weeks, the current sync rate is around 0.5 blocks per second. So at this rate the final 1,500,000 blocks will take an additional 34 days to sync.

I'm not sure what else I could do to improve the syncing speed. I'm assuming the bottleneck is the disk I/O (although I haven't tried syncing with more than 4 CPUs).

Is there anything I'm doing wrong here or is this the normal sync rate for the archive mode?

Parity node configuration:

    [parity]
    mode = "active"
    base_path = "/data"
    db_path = "/data/chains"
    keys_path = "/data/keys"

    [rpc]
    interface = "0.0.0.0"
    cors = ["all"]
    hosts = ["all"]
    apis = ["all"]

    [websockets]
    interface = "0.0.0.0"
    origins = ["all"]
    apis = ["all"]
    hosts = ["all"]

    [ui]
    interface = "0.0.0.0"

    [footprint]
    tracing = "off"
    pruning = "archive"
    db_compaction = "ssd"
    cache_size = 1024

Edit:

Parity logs usually show around 100 tx/s and around 1 blk/s:

2019-01-15 18:45:40 UTC Syncing #5370998 0xbe04…7731     0.90 blk/s   98.1 tx/s    5 Mgas/s      0+  482 Qed  #5371481   47/50 peers    129 MiB chain   14 MiB db   43 MiB queue  105 MiB sync  RPC:  0 conn,    0 req/s,    0 µs
2019-01-15 18:45:50 UTC Syncing #5371009 0x028b…c34e     1.10 blk/s  141.5 tx/s    7 Mgas/s      0+  470 Qed  #5371481   46/50 peers    131 MiB chain   15 MiB db   41 MiB queue  105 MiB sync  RPC:  0 conn,    0 req/s,    0 µs
2019-01-15 18:46:00 UTC Syncing #5371019 0x466e…c188     1.00 blk/s  108.4 tx/s    6 Mgas/s      0+  458 Qed  #5371481   46/50 peers    132 MiB chain   15 MiB db   40 MiB queue  105 MiB sync  RPC:  0 conn,    0 req/s,    0 µs

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.