Comments

For those interested. I built from source and used geth on the same Windows machine for comparison. I started full node with geth on 20170407 and by 20170410 it loaded 41.2 Gb of data, which amounts to about 2.3 mln blocks (out of ~3.5 mln) i.e. about 65%.I found that the synchronisation becomes progressively slower, the bigger the database grows. At the start it took geth just 3 hours to load 1 mln blocks/~9.5Gb. For the last night it only got from 40.9Gb to 41.2Gb i.e. absolutely dramatic slowdown. I wonder if is it because of Patricia Tree insert inefficiency?Another thing to notice is that sometime number of peer nodes drops to 2-3, at which point the synchronization cannot proceed.When I'm done with geth, I'll test eth again. May be everything is just the way it's supposed to be.

block number range: sync speed, blocks/hour------------------------------------------0..1045923 348,6411045923..1726874 54,1291726874..2322736 15,7772322736..2344564 1,175 : To me it looks like a Fundamental problem with the blockchain. Pretty much exponential drop in sync speed as the datastore size grows.There is still more than a million blocks to go and the speed by now is measly 1000 blocks per hour. Even without further drop in speed it'll take 1000 hours to get to the finish. If the drop continues, it may never happen. That's with just 3.5 mln blocks. What about 3.5 bln?My laptop has i7, 2.20Ghz, 4 cores, 12Gb RAM and a broadband connection.I see on the Net mentioning RaspberryPi for the Full node. I guess that's a history by now. When it'll come (if ever) to 3.5 bln blocks, one will need a supercomputer for a full node.