First synchronisation takes hours of 100% CPU #2813

issue stairjoke opened this issue on July 3, 2013

stairjoke commented at 11:40 PM on July 3, 2013: none

On Mac OS X 10.8.4 with an intel core i7 and 16GB RAM it takes almost constantly 70% CPU during first/initial synchronisation - total sync time about 16h. Konsole log repeats "Misbehaving…"

Misbehaving: [IP ADDRESS]:8333 (0 -> 0) stored orphan tx … (mapsz 569) received block … ERROR: ProcessBlock() : already have block … …
Diapolo commented at 12:31 PM on July 5, 2013: none

That is not an error and normal behaviour.
stairjoke commented at 1:28 PM on July 5, 2013: none

But is the 16h long 70% CPU normal?
laanwj commented at 5:48 AM on July 9, 2013: member

You can use -par=1 to only use one thread for verification. This brings down the % but also slows down the sync.
stairjoke commented at 8:46 PM on July 9, 2013: none

Thanks, but it finished 4 days ago and 3 days ago it told me that my blocks are corrupt and wanted to resynchronise. So now I'm just using an online service as wallet, because I don't want to del with it.
stairjoke closed this on Jul 9, 2013
sipa commented at 9:04 PM on July 9, 2013: member

Just a side note: you can run a local client which doesn't need the full block chain - that is only needed to participate in validation of the network. Clients like MultiBit or Electrum also work locally (=you're the sole owner of the keys to spend coins) but only synchronize transactions relevant to your wallet (minutes or seconds to sync).
Bushstar referenced this in commit aeba4afce9 on Apr 5, 2019
Bushstar referenced this in commit 66c2f39531 on Apr 8, 2020
bitcoin locked this on Sep 8, 2021

Contributors