How much data does the blockchain take up on your computer?

[BitcoinZAR]

How much space does the blockchain take up on your hard drive at the moment, and what is the daily download in data?

[LiteCoinGuy]

Should be about 44 GB.

[BitcoinZAR]

Do you know how much data it uses daily? I am using 3G mobile data, and its expensive, but I want to run qt so that I can do some development tutorials....It would help me budget if I knew what the daily data usage would likely be

[arnoudk]

Diskspace takes about 55 GB - 60 GB right now.

Code: Select all

/data/bitcoind # du -m --max-depth=1 1129 ./chainstate 1 ./database 56278 ./blocks 57413 .

If you do not accept incoming connections, your data traffic would be limited, but if your data is expensive it might be a bad idea still:

Code: Select all

bitcoin-cli getnettotals { "totalbytesrecv" : 1631591412, "totalbytessent" : 957773612, "timemillis" : 1445395189640 }

If you accept incoming connections, you would use much much more data. This is from one of the public nodes I run:

Code: Select all

Usage kB/s: 19 kB/s (recv), 386 kB/s (sent). 1:19 Cumulative: 31368 MB (recv), 282837 MB (sent). 1:9 Peers : 61 in, 8 out. 1:7 Mempool : 9936 items, 110 MB.

Outgoing traffic is now only 386 kB/s, but it peaks at 3 MB/s for this node.

There are patches developed (see the bitcoin xt mailing list) that allows you to limit datatraffic. You could of course also do this in QoS settings for your router / devices.

Hope this helps.

[BitcoinZAR]

Thanks for the info, yes it does help

[arnoudk]

Thanks for the info, yes it does help

You're welcome. I was not quite satisfied myself yet with the comparison between a node that accepts inbound connections as compared to a node that only has outbound connections. So I compared my local node (on a painfully slow internet line) to my remote data center-hosted server. These are the statistics of the last 60 minutes:

Local node (no inbound connections, 3 outbound connections specified):

Code: Select all

Usage kB/s: 4 kB/s (recv), 0 kB/s (sent). 1:0 Cumulative: 47 MB (recv), 19 MB (sent). 60 min. 1:0 Reported : 178 MB (recv), 67 MB (sent). 1:0 Peers : 0 in, 3 out. 1:0 Mempool : 9468 items, 108 MB.

Remote node (with inbound connections enabled)

Code: Select all

Usage kB/s: 9 kB/s (recv), 46 kB/s (sent). 1:4 Cumulative: 123 MB (recv), 798 MB (sent). 60 min. 1:6 Reported : 35036 MB (recv), 318571 MB (sent). 1:9 Peers : 55 in, 8 out. 1:6 Mempool : 10000 items, 122 MB.

The local node received 47 MB and sent 19 MB. The remote node received 123 MB and sent 798 MB.

My previous measurement was not quite correct, as I measured the local node that I use as a 'gateway node'. It is the only outgoing node to the bitcoin network, but gets connected to on the local network by other machines. The internal LAN traffic was counted in my previous response, and that is not fair. It is not included here.

I noticed that, when the bitcoin network gets tx flooded, my downlink can get saturated. I can afford to just switch off the bitcoin gateway process if it annoys me, and I have not yet implemented the traffic shaping patches that are available.

Just out of curiosity, what is the network like in South Africa? What are you able to send/receive?

[arnoudk]

I just installed Bitcoin XT 0.11.0.D from the github master branch on my local node. I have really limited bitcoind using the RFC functionality at 10 kB/s for both upstream and downstream:

The RFC has two new functions

Code: Select all

== Network == addnode "node" "add|remove|onetry" getaddednodeinfo dns ( "node" ) getconnectioncount getnettotals getnetworkinfo getpeerinfo gettrafficshaping <=== ping settrafficshaping "send|receive" "burstKB" "averageKB" <===

Setting via:

Code: Select all

bitcoin-cli settrafficshaping send 10 10

and

Code: Select all

bitcoin-cli settrafficshaping receive 10 10

Checking via:

Code: Select all

bitcoin-cli gettrafficshaping { "sendburst" : 10, "send" : 10, "receiveburst" : 10, "receive" : 10 }

It works very well so far. I'll probably have to increase 10 kB/s to something more realistic, but now I do not notice bitcoind running in the background on a slow network.

Note that it is recommended to set the burstKB to a higher value than averageKB, ie 10x as high.

I'll probably add a crontab to increase the limits at night and reset the limits in the morning, if needed.