I've tried resetting the sync and it still comes to a screeching halt around block number 2.4m. I know about the attacks on Ethereum around those blocks, but this is ridiculous:
I've been syncing for 4 days now, the first day I went from #0 to about #2.2m second day I got to ~#2.4m and the last 2 days it hasn't even got half way to #2.5m. Isn't Parity supposed to be significantly faster than this? I tried syncing with Geth first and it got permanently stuck at 141 blocks left in the same time it's taken parity to slow down to a highway parking lot. Now I can't even get Geth to get back to where it was, since I reset it anyway. Is there any other options to get this thing synced faster? Like downloading someone else's block chain copy or something?
This is how I run Parity: parity --min-peers=50 --max-peers=100 --cache 4096 --geth
By the end of the 6th day, it sped back up because it past the troubled range. Now it's stalled again with less than 200k blocks left. Yay me. Any ideas?
I'm being totally serious when I say that the best thing to do is simply be patient. As long as you're getting new blocks, there's not much to do. If on the other hand, Parity continues to report the same block, then you can kill it and restart it.
Blocks between around ~2286900 and ~271800 are very, very slow because of the DDOS attack in Sept/Oct 2016. What happens is the blocks are very long playing, so if you repeatedly kill the node while it's processing a block and restart it, you're making it take that much longer because it has to start over on that block. Once it gets past ~271800 it should speed up again.
I'm in the home stretch right now syncing with Parity v1.7.3 and it's been going now for almost 24hrs. At its current rate of about 2-5blks/s it probably has another 20 hrs to go. I agree with current responses that you just have to wait it out. In my research I've seen a lot of responses focus on the computer, especially the HDD but this clearly seems to me to be a limitation of the Ethereum network peers.
When you think about it you're getting that data piecemeal from distributed peers. It's nothing like downloading a large file from a server. My system is connected with about 25 peers. Those are nodes that are probably very busy trying to mine Eth and aren't going to focus on getting you or me up to date so we can compete with them. I'm not saying they altered their code, but a review of the code might help explain the slowness to sync.
I've heard that you can find compressed files of the back blocks and download the file and install it to sync more quickly. Anyone know if that works?