Quote from: uxgpf on September 16, 2015, 06:04:39 PM

Quote from: adamstgBit on September 16, 2015, 05:52:32 PM

Quote from: uxgpf on September 16, 2015, 05:49:30 PM

Quote from: adamstgBit on September 16, 2015, 05:34:10 PM

home full nodes are already pushing limits, its not hard to argue that a slow increase in blocksize is necessary, but how slow? let demand determine that...

I don't agree with this. It would be true only if average user runs 90s 56k modem.
Even 1 Mb internet connection works fine. (Though initial sync would take few days, but you only need to do that once.)

the data is currently redundantly received and transmitted again and again.
run a full node yourself and get back to me.

I'm running one. Currently 31 connections, 5.5 kB/s down 9.2 kB/s up.

[edit] Killed the node while fiddling with it...so now only 15 connections. Anyway, here's some more numbers.

Code:

Every 10.0s: bitcoin-cli getinfo Wed Sep 16 21:21:33 2015

{
   "version" : 110000,
   "protocolversion" : 70010,
   "blocks" : 374827,
   "timeoffset" : -1,
   "connections" : 15,
   "proxy" : "",
   "difficulty" : 56957648455.01000977,
   "testnet" : false,
   "relayfee" : 0.00001000,
   "errors" : ""
}

download and upload bandwidth used (just a snapshot...averages could differ):

Code:

$ awk '{if(l1){print ($2-l1)/1024"kB/s",($10-l2)/1024"kB/s"} else{l1=$2; l2=$10;}}' <(grep wlan0 /proc/net/dev) <(sleep 1; grep wlan0 /proc/net/dev)
2.67871kB/s 3.96973kB/s

interesting,

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