1

I am using a raspberry pi to download the archived version of the blockchain with parity. I've started parity with

parity -d /home/xxx/data/Ethereum --pruning archive --public-node

However, the synchronisation is running at 0-5 blocks per second. At this rate, it won't finish for 1-2 years.

Is there a setting that I can use to speed this up. For example, if I reduced the --max-peers to 10 would it speed up the synchronisation? Or is this an unachievable feat for a Pi?

  • 1
    I don't know how you can speed it up on a Raspberry Pi, but is it feasible in your situation to sync on another machine and then move the synced chain to the Pi? – lungj Aug 23 '17 at 12:52
  • @lungj yes, it is possible for me to sync elsewhere but I have a feeling an archive sync will take over a day - longer than i'm willing to leave my desktop on for. I had some feedback from the parity channel that compiling locally might resolve the issue. I'll update with the result when it's done. – forgetso Aug 24 '17 at 13:23
0

It's more likely to take 10-20 years on a Raspberry Pi given the current Ethereum blockchain utilization with more than 400k transactions per day.

Even on commodity hardware it's taking weeks to complete an archive sync due to the spam blocks in autumn 2016.

The most obvious way to get this done is attaching the external drive which is hopefully an SSD with at least 500 GB to some fast machine, sync up in archive mode and once finished, mount it on your Raspberry Pi and attach it with --db-path.

  • Thanks for the comment, I'm at 2.2M blocks and syncing on a 1TB external so it will be no problem for me to switch this to my desktop if it takes too long. FYI - building parity from source has sped it up by quite a bit. – forgetso Aug 30 '17 at 8:04
  • Good to know... – Waqar Lim Aug 30 '17 at 9:43

Your Answer

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

Not the answer you're looking for? Browse other questions tagged or ask your own question.