Quote from: uxgpf on September 16, 2015, 07:25:48 PM

Quote from: adamstgBit on September 16, 2015, 06:56:26 PM

Quote from: uxgpf on September 16, 2015, 06:54:23 PM

Quote from: adamstgBit on September 16, 2015, 06:38:23 PM

interesting,

i'm currently syncing myself a full node to test this out myself.

Worst thing about synching is that CPU usage. I swear I could have fried eggs on my computer case while it was doing it. Had to actually open the balcony door as I feared it would overheat and shut itself down.

Seems like this bandwidth usage varies a lot. Those numbers for 31 connections were BS as I'm getting more with 20 now. (had some jumps to 25 kB/s) also updated the snippet with with 15-16 connections in previous post.

Maybe I should write a script and let it run for few hours to count averages with connections fixed to some value (I guess this can be set in config file.)

It would give a better idea of the bandwidth needs. I just have to remember not to download any pron while I'm at it.

yup, i'll try something like that too.

Number of max connections can be set in ~/.bitcoin/bitcoin.conf:

Code:

# Maximum number of inbound+outbound connections.
maxconnections=20

If you are behind NAT it will only use 8 outbound connections unless you open/forward a port (TCP 8333) on your router for it.

i guess the more connections the more bandwidth i'll be using

i'll keep it at the default and see what the gives.