I am using Amazon Web Services (AWS)'s 1 GiB RAM free instance. I have private Ethereum network, which has around 1,500,000 blocks, but most blocks are empty. There is not much transactions exist and chain is around 1 GiB size.
First I was syncing without using
--warp flag. Based on suggestions, I used
--warp and it get much much slower. Now it is almost 5 hours and I am still on 300,000 th block.
The way I run parity node:
parity --warp --geth --chain /home/ubuntu/EBloc/parity.json --network-id 23422 --reserved-peers /home/ubuntu/EBloc/myPrivateNetwork.txt --jsonrpc-apis web3,eth,net,parity,parity_accounts,traces,rpc,parity_set --author $COINBASE --rpccorsdomain=* --mode active --tracing off --pruning fast --db-compaction ssd --cache-size 1024
[Q] Why migh
Parity sycn that slow?
--warp did not make any speed-up instead it make syncing operation much slow.
[Q] I have up-to-date chain on my server machine. Would it be possible to copy-paste/migrate the
Parity's chain database (
/home/ubuntu/.local/share/io.parity.ethereum) I already have into AWS instance, since copy-paste operation is much faster than the syncing operation?
ubuntu@space:~/.local/share/io.parity.ethereum$ ls chains dapps keys network signer
Thank you for your valuable time and help.