Slow Syncing Ubuntu

[Enzyme]

Hi,

I've purchased a VPS and it's running bitcoind.

It's currently synced to block 187xxx and it has seemed to slow down a lot.
How can I speed it up? I did a speed test and it has a 100mb connection.

[1714556790]

1714556790

[Newar]

If you think it's bandwidth related you can speed it up using the torrent bootstrap.dat or using the latest release candidate 0.10.0. From my observation however it is normal for it to slow down the closer it gets to the latest block. Also remember it is validating the whole blockchain, so your VPS' hardware specs matter too.

[shorena]

If you think it's bandwidth related you can speed it up using the torrent bootstrap.dat or using the latest release candidate 0.10.0. From my observation however it is normal for it to slow down the closer it gets to the latest block. Also remember it is validating the whole blockchain, so your VPS' hardware specs matter too.

This or hammer another node with a fast connection. Versions prior to 0.10.0 can only sync with a single node.
Make sure you stop bitcoind first and start it with:
bitcoind connect=213.165.91.169

the above IP is my node, you can also take one from the list below:

Code:

last updated 2015.01.11
---------------------------------------------------------------------------------------------------
IP                  - location             - owner[1]  -  speed      - info/stats page[2] - testnet
---------------------------------------------------------------------------------------------------
84.200.34.113       - Freinsheim, DE, EU   - Newar     - 1000 mbit/s - yes                - no
185.45.192.129      - Amsterdam, NL, EU    - anon      - 1000 mbit/s - /node.php[3]       - yes
94.23.146.127       - NL, EU               - anon      -  200 mbit/s - /status            - no
213.165.91.169      - Germany, EU          - shorena   -  100 mbit/s - yes                - no
191.236.50.217      - Virgina, US          - grue      -  100 mbit/s - no                 - no
---------------------------------------------------------------------------------------------------
!!The following nodes have been unreachable at the time of the last update and might[5] be down!!
---------------------------------------------------------------------------------------------------
eldinhadzic.org[4]  - LA, USA              - eldinhadz - 1000 mbit/s - no                 - no
50.7.68.180         - New York, USA        - Newar     -  100 mbit/s - yes                - no
5.9.24.81           - Germany, EU          - zvs       -  unknown    - no                 - no
178.79.173.71       - United Kingdom, EU   - zvs       -  unknown    - no                 - no
107.155.104.194     - Dalls, USA           - zvs       -  unknown    - no                 - no
106.185.32.195      - Japan, Asia          - zvs       -  unknown    - no                 - no
94.242.57.173       - Russia, Asia         - zvs       -  unknown    - no                 - no
---------------------------------------------------------------------------------------------------
[1] refers to a bitcointalk.org username or anon if requested
[2] same IP, port 80 or path/port given
[3] work in progress
[4] IP is 173.236.158.177
[5] or reached max connections at the time of testing

[scientific]

Most VPS's are overcrowded with other customers anyway, so it'll have poor performance. You may have a fast connection, but must of the time is spent in verifying the blocks (CPU and HDD time), therefore it's normal.

[zvs]

If you think it's bandwidth related you can speed it up using the torrent bootstrap.dat or using the latest release candidate 0.10.0. From my observation however it is normal for it to slow down the closer it gets to the latest block. Also remember it is validating the whole blockchain, so your VPS' hardware specs matter too.

This or hammer another node with a fast connection. Versions prior to 0.10.0 can only sync with a single node.
Make sure you stop bitcoind first and start it with:
bitcoind connect=213.165.91.169

the above IP is my node, you can also take one from the list below:

Code:

last updated 2015.01.11
---------------------------------------------------------------------------------------------------
IP                  - location             - owner[1]  -  speed      - info/stats page[2] - testnet
---------------------------------------------------------------------------------------------------
84.200.34.113       - Freinsheim, DE, EU   - Newar     - 1000 mbit/s - yes                - no
185.45.192.129      - Amsterdam, NL, EU    - anon      - 1000 mbit/s - /node.php[3]       - yes
94.23.146.127       - NL, EU               - anon      -  200 mbit/s - /status            - no
213.165.91.169      - Germany, EU          - shorena   -  100 mbit/s - yes                - no
191.236.50.217      - Virgina, US          - grue      -  100 mbit/s - no                 - no
---------------------------------------------------------------------------------------------------
!!The following nodes have been unreachable at the time of the last update and might[5] be down!!
---------------------------------------------------------------------------------------------------
eldinhadzic.org[4]  - LA, USA              - eldinhadz - 1000 mbit/s - no                 - no
50.7.68.180         - New York, USA        - Newar     -  100 mbit/s - yes                - no
5.9.24.81           - Germany, EU          - zvs       -  unknown    - no                 - no
178.79.173.71       - United Kingdom, EU   - zvs       -  unknown    - no                 - no
107.155.104.194     - Dalls, USA           - zvs       -  unknown    - no                 - no
106.185.32.195      - Japan, Asia          - zvs       -  unknown    - no                 - no
94.242.57.173       - Russia, Asia         - zvs       -  unknown    - no                 - no
---------------------------------------------------------------------------------------------------
[1] refers to a bitcointalk.org username or anon if requested
[2] same IP, port 80 or path/port given
[3] work in progress
[4] IP is 173.236.158.177
[5] or reached max connections at the time of testing

bit late reply, but ...

yeah, I cancelled all my servers a couple months ago.  Lost interest in bitcoins since I'm not an ASIC manufacturer and my primary reason for messing w/ them in the first place was profit.  Unsure who owns 5.9.24.81 now.

I have a few servers now but way too underpowered to run bitcoind.  I've been thinking of grabbing another Hetzner though, considering how cheap they are now w/ the weak euro ..  Something like $30/mo for an i7-3770, 16GB RAM, 2x3TB HDD... and $3 or so more for 32GB RAM...  damn.

[shorena]

-snip-
bit late reply, but ...

yeah, I cancelled all my servers a couple months ago.  Lost interest in bitcoins since I'm not an ASIC manufacturer and my primary reason for messing w/ them in the first place was profit.  Unsure who owns 5.9.24.81 now.

I have a few servers now but way too underpowered to run bitcoind.  I've been thinking of grabbing another Hetzner though, considering how cheap they are now w/ the weak euro ..  Something like $30/mo for an i7-3770, 16GB RAM, 2x3TB HDD... and $3 or so more for 32GB RAM...  damn.

Thanks for the update, I removed them. Looks like Newar is out as well. Either that or the servers are overcrowded

[cr1776]

bit late reply, but ...

yeah, I cancelled all my servers a couple months ago.  Lost interest in bitcoins since I'm not an ASIC manufacturer and my primary reason for messing w/ them in the first place was profit.  Unsure who owns 5.9.24.81 now.

I have a few servers now but way too underpowered to run bitcoind.  I've been thinking of grabbing another Hetzner though, considering how cheap they are now w/ the weak euro ..  Something like $30/mo for an i7-3770, 16GB RAM, 2x3TB HDD... and $3 or so more for 32GB RAM...  damn.

I found a 4GB (5GB burstable) RAM, 5000GB bandwidth, 150 GB RAID 10, 4 cores for $99/year and moved a server (my bitcoind server) there in early January.  I figured for $99/year it was a good way to support the network.  And make sure that my tech skills don't get too rusty.

It isn't as powerful as the server above, but after 27 days uptime on the new server it has stabilized at about 76% of RAM used, and 46.6 GB/150GB disk with 433 connections as of 10 seconds ago.

With server prices dropping every year, I often switch in January if I find a better deal on one server.  

The scene sure has changed since end of 2010/beginning of 2011!

[Newar]

[...] Looks like Newar is out as well. Either that or the servers are overcrowded

Still around    Just did some maintenance on 84.200.34.113 today. Apart from that, AFAICT, it's been up all the time.

50.7.68.180 is now new at 23.92.214.123, however no more status page at the moment, as it's running btcd.
https://getaddr.bitnodes.io/nodes/?q=23.92.214.123

[shorena]

[...] Looks like Newar is out as well. Either that or the servers are overcrowded

Still around    Just did some maintenance on 84.200.34.113 today. Apart from that, AFAICT, it's been up all the time.

50.7.68.180 is now new at 23.92.214.123, however no more status page at the moment, as it's running btcd.
https://getaddr.bitnodes.io/nodes/?q=23.92.214.123

Thanks for the update.

Code:

last updated 2015.02.01
---------------------------------------------------------------------------------------------------
IP                  - location             - owner[1]  -  speed      - info/stats page[2] - testnet
---------------------------------------------------------------------------------------------------
185.45.192.129      - Amsterdam, NL, EU    - anon      - 1000 mbit/s - /node.php[3]       - yes
84.200.34.113       - Freinsheim, DE, EU   - Newar     - 1000 mbit/s - yes                - no
94.23.146.127       - NL, EU               - anon      -  200 mbit/s - /status            - no
213.165.91.169      - Germany, EU          - shorena   -  100 mbit/s - yes                - no
191.236.50.217      - Virgina, US          - grue      -  100 mbit/s - no                 - no
50.7.68.180  [5]    - New York, USA        - Newar     -  100 mbit/s - yes                - no
---------------------------------------------------------------------------------------------------
!!The following nodes have been unreachable at the time of the last update and might[4] be down!!
---------------------------------------------------------------------------------------------------
-
---------------------------------------------------------------------------------------------------
[1] refers to a bitcointalk.org username or anon if requested
[2] same IP, port 80 or path/port given
[3] work in progress
[4] or reached max connections at the time of testing. Nodes failing 3 tests in a row will
be removed (Number of failed test is noted behind the IP)
[5] Runs BTCD (alternative full node implemenation with GO)

[Newar]

FTFY

Code:

last updated 2015.02.01
---------------------------------------------------------------------------------------------------
IP                  - location             - owner[1]  -  speed      - info/stats page[2] - testnet
---------------------------------------------------------------------------------------------------
185.45.192.129      - Amsterdam, NL, EU    - anon      - 1000 mbit/s - /node.php[3]       - yes
84.200.34.113       - Freinsheim, DE, EU   - Newar     - 1000 mbit/s - yes                - no
94.23.146.127       - NL, EU               - anon      -  200 mbit/s - /status            - no
213.165.91.169      - Germany, EU          - shorena   -  100 mbit/s - yes                - no
191.236.50.217      - Virgina, US          - grue      -  100 mbit/s - no                 - no
23.92.214.123  [5]  - Rochester, USA       - Newar     -  100 mbit/s - no                 - no
---------------------------------------------------------------------------------------------------
!!The following nodes have been unreachable at the time of the last update and might[4] be down!!
---------------------------------------------------------------------------------------------------
-
---------------------------------------------------------------------------------------------------
[1] refers to a bitcointalk.org username or anon if requested
[2] same IP, port 80 or path/port given
[3] work in progress
[4] or reached max connections at the time of testing. Nodes failing 3 tests in a row will
be removed (Number of failed test is noted behind the IP)
[5] Runs BTCD (alternative full node implementation with GO)

[shorena]

FTFY
-snip-

Even the typo, thanks

FYI: 23.92.214.123 runs an apache2 in default mode

[zvs]

Aha, I've got a node running again at 46.4.65.207.  Should be around for at least several months.  Don't use bandwidth for anything else, so fine for people to DL blockchain from it.

[Newar]

Aha, I've got a node running again at 46.4.65.207.  Should be around for at least several months.  Don't use bandwidth for anything else, so fine for people to DL blockchain from it.

Welcome back! In case you missed it, there is a lottery going on: https://getaddr.bitnodes.io/nodes/incentive/

[shorena]

Aha, I've got a node running again at 46.4.65.207.  Should be around for at least several months.  Don't use bandwidth for anything else, so fine for people to DL blockchain from it.

200Mbit/s, in Berlin?

[zvs]

Aha, I've got a node running again at 46.4.65.207.  Should be around for at least several months.  Don't use bandwidth for anything else, so fine for people to DL blockchain from it.

200Mbit/s, in Berlin?

Falkenstein, Saxony-Anhalt... about 150 miles SW of Berlin, I think.

It's on a gigabit port, I've seen it burst up to 1000Mbit/s upstream on new blocks.  It can sustain at least 500Mbit, didn't want to go higher than that, since I had one null routed about a year ago for an uncapped torrent (said outgoing DDoS or something).

[shorena]

Aha, I've got a node running again at 46.4.65.207.  Should be around for at least several months.  Don't use bandwidth for anything else, so fine for people to DL blockchain from it.

200Mbit/s, in Berlin?

Falkenstein, Saxony-Anhalt... about 150 miles SW of Berlin, I think.

It's on a gigabit port, I've seen it burst up to 1000Mbit/s upstream on new blocks.  It can sustain at least 500Mbit, didn't want to go higher than that, since I had one null routed about a year ago for an uncapped torrent (said outgoing DDoS or something).

Updated the list accordingly, thanks

Code:

last updated 2015.02.14
---------------------------------------------------------------------------------------------------
IP                  - location             - owner[1]  -  speed      - info/stats page[2] - testnet
---------------------------------------------------------------------------------------------------
185.45.192.129      - Amsterdam, NL, EU    - anon      - 1000 mbit/s - /node.php[3]       - yes
84.200.34.113       - Freinsheim, DE, EU   - Newar     - 1000 mbit/s - yes                - no
46.4.65.207         - Falkenstein, DE, EU  - zvs       -  500 mbit/s - no                 - no
94.23.146.127       - NL, EU               - anon      -  200 mbit/s - /status            - no
213.165.91.169      - Germany, EU          - shorena   -  100 mbit/s - yes                - no
191.236.50.217      - Virgina, US          - grue      -  100 mbit/s - no                 - no
23.92.214.123  [5]  - Rochester, USA       - Newar     -  100 mbit/s - no                 - no
---------------------------------------------------------------------------------------------------
!!The following nodes have been unreachable at the time of the last update and might[4] be down!!
---------------------------------------------------------------------------------------------------
-
---------------------------------------------------------------------------------------------------
[1] refers to a bitcointalk.org username or anon if requested
[2] same IP, port 80 or path/port given
[3] work in progress
[4] or reached max connections at the time of testing. Nodes failing 3 tests in a row will
be removed (Number of failed test is noted behind the IP)
[5] Runs BTCD (alternative full node implementation with GO)