Topic: Bitcoind syncing taking way too long (Read 923 times)

http://gtf.org/garzik/bitcoin/bootstrap.dat.torrent

Finally! I figured out the issue. It was a problem with my router. I ran speed tests and found I was only getting about 1 Mbps upload. When I bypassed the router and plugged it straight into the modem, I was getting 4.3 Mbps upload. My router had Upstream Bandwidth set to Auto in QoS, which for some reason was limiting it to about 1 Mbps. So bitcoind was using my router's full upload limit and killing my download speeds or something dumb like that. I changed Upstream Bandwidth in router management to Manual and set it to 50000 Kbps, so now speed tests show I am getting my full upload speeds with the router, about 4.3 Mbps. Now bitcoind is downloading perfectly again. Son of a bitch that was a pain in the ass to figure out what was wrong.

I am attempting to get my linux machine fully synced, and am running into issues. I keep having to stop and restart bitcoind, and reboot the machine. It has 8GB ram, SSD, and an i5 3337U 1.8GHz CPU. It is running ubuntu 14.04.1 64 bit (fresh install, with only bitcoind and a couple other smaller services). Top shows bitcoind is only using 1% CPU and 7.1% RAM at the moment, and syncing extremely slow. It's currently on block 231095. I started the initial sync yesterday, so it has been about 24 hours now. Every once in a while it just stops syncing. I can run bitcoind getinfo and it will show that it is on the same block as it was about 5 minutes ago. I don't get this, because even my VPS with low RAM have synced faster than this. Any ideas of what to do or try? And why is it using so little resources (I still have 6GB RAM free and only using 3% of the CPU at the moment)

Edit: I just ran nload and it is weird. My incoming (downloading blockchain) is only showing about 150kBit/s, while outgoing (uploading blockchain to other nodes?) is at 1.3MBit/s... I am uploading more than downloading???


I have opened port 8333, and set QoS on 8333 to highest, so I am out of ideas here. Am I just getting connected to really slow nodes or something?

Another edit: I am guessing this isn't normal behavior, correct? 5 minutes for 23 blocks?