Extremely slow initial sync, spam of “already have block” errors. #3243

1. 
   shahnah commented at 9:43 am on November 13, 2013: none

   There’s a lot of ProcessBlock() “already have block x” errors being created in my initial sync. Is this due to configuration, network latency, operating system? Is it even something I need to be worried about? There’s not a heap of information around as to what is going on, but from reading the forums, peers shouldn’t even be sending me orphan blocks at all during the initial sync (as they know they’re orphans).

   Debug.log - ProcessBlock() error spam “already have block”

   Debug.log - attempt with a later build, many orphan blocks not no particular reason (I assume it’s related)

   I’m running OSX Mavericks, with a SSD, plenty of memory, and a bitcoind build at the time of commit cd696e64dfe8821fe13d959dd2d1a2ee892f9155.

2. 
   fanquake commented at 11:41 am on November 13, 2013: member

   Your probably experiencing the effects of the Mavericks App Nap feature. You’ll need to right click the Bitcoin app and choose Get Info, then Prevent App Nap. See #3182 for a further explanation.
3. 
   shahnah commented at 11:55 am on November 13, 2013: none

   bitcoind in my case is running as a daemon, and they’re not affected by App Nap.

   Good call though, it’s something I’ve been running into quite often with other apps. Useful feature, but not when you’re doing something intentionally CPU intensive.

4. 
   laanwj commented at 12:09 pm on January 10, 2014: member

   This is as expected. You probably got some bad peers. Headers-first sync is going to improve this.

   In the mean time you can use jgarzik’s block chain torrent for a faster initial sync: https://bitcointalk.org/index.php?topic=145386.0

5. laanwj closed this on Jan 10, 2014

   ---

6. DrahtBot locked this on Sep 8, 2021

Contributors
shahnah fanquake laanwj