📅 Original date posted:2015-07-23
📝 Original message:You may see much better throughput if you run a few servers around the
globe and test based on closest-by-geoip. TCP throughput is rather
significantly effected by latency, though I'm not really sure what you
should be testing here, ideally.
On 07/23/15 14:19, slurms--- via bitcoin-dev wrote:
> On this day, the Bitcoin network was crawled and reachable nodes surveyed to find their maximum throughput in order to determine if it can safely support a faster block rate. Specifically this is an attempt to prove or disprove the common statement that 1MB blocks were only suitable slower internet connections in 2009 when Bitcoin launched, and that connection speeds have improved to the point of obviously supporting larger blocks.
>
>
> The testing methodology is as follows:
>
> * Nodes were randomly selected from a peers.dat, 5% of the reachable nodes in the network were contacted.
>
> * A random selection of blocks was downloaded from each peer.
>
> * There is some bias towards higher connection speeds, very slow connections (<30KB/s) timed out in order to run the test at a reasonable rate.
>
> * The connecting node was in Amsterdam with a 1GB NIC.
>
>
> Results:
>
> * 37% of connected nodes failed to upload blocks faster than 1MB/s.
>
> * 16% of connected nodes uploaded blocks faster than 10MB/s.
>
> * Raw data, one line per connected node, kilobytes per second http://pastebin.com/raw.php?i=6b4NuiVQ
>
>
> This does not support the theory that the network has the available bandwidth for increased block sizes, as in its current state 37% of nodes would fail to upload a 20MB block to a single peer in under 20 seconds (referencing a number quoted by Gavin). If the bar for suitability is placed at taking only 1% of the block time (6 seconds) to upload one block to one peer, then 69% of the network fails for 20MB blocks. For comparison, only 10% fail this metric for 1MB blocks.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
Matt Corallo [ARCHIVE] /
npub1e4…jxmcu
2023-06-07 15:43:21
in reply to nevent1q…7kxs
Author Public Key
npub1e46n428mcyfwznl7nlsf6d3s7rhlwm9x3cmkuqzt3emmdpadmkaqqjxmcuPublished at
2023-06-07 15:43:21Event JSON
{
"id": "7d18b80a3b3468a728a26e17f8e627530af49ab721f49322c3ab2111479953df",
"pubkey": "cd753aa8fbc112e14ffe9fe09d3630f0eff76ca68e376e004b8e77b687adddba",
"created_at": 1686152601,
"kind": 1,
"tags": [
[
"e",
"db0eb2204009a6b618d874147fda66733ace7abb340d9450e85ebe8e0a9d6b6a",
"",
"root"
],
[
"e",
"001ab33a408d896871d9063cffa0d23e0f5d83b42cdcb691615a84d4a30b498e",
"",
"reply"
],
[
"p",
"d1e5e343064328be063c36deb0dacb660b8589dcbca90112f9c449503b63ebba"
]
],
"content": "📅 Original date posted:2015-07-23\n📝 Original message:You may see much better throughput if you run a few servers around the\nglobe and test based on closest-by-geoip. TCP throughput is rather\nsignificantly effected by latency, though I'm not really sure what you\nshould be testing here, ideally.\n\nOn 07/23/15 14:19, slurms--- via bitcoin-dev wrote:\n\u003e On this day, the Bitcoin network was crawled and reachable nodes surveyed to find their maximum throughput in order to determine if it can safely support a faster block rate. Specifically this is an attempt to prove or disprove the common statement that 1MB blocks were only suitable slower internet connections in 2009 when Bitcoin launched, and that connection speeds have improved to the point of obviously supporting larger blocks.\n\u003e \n\u003e \n\u003e The testing methodology is as follows:\n\u003e \n\u003e * Nodes were randomly selected from a peers.dat, 5% of the reachable nodes in the network were contacted.\n\u003e \n\u003e * A random selection of blocks was downloaded from each peer.\n\u003e \n\u003e * There is some bias towards higher connection speeds, very slow connections (\u003c30KB/s) timed out in order to run the test at a reasonable rate.\n\u003e \n\u003e * The connecting node was in Amsterdam with a 1GB NIC. \n\u003e \n\u003e \n\u003e Results:\n\u003e \n\u003e * 37% of connected nodes failed to upload blocks faster than 1MB/s.\n\u003e \n\u003e * 16% of connected nodes uploaded blocks faster than 10MB/s.\n\u003e \n\u003e * Raw data, one line per connected node, kilobytes per second http://pastebin.com/raw.php?i=6b4NuiVQ\n\u003e \n\u003e \n\u003e This does not support the theory that the network has the available bandwidth for increased block sizes, as in its current state 37% of nodes would fail to upload a 20MB block to a single peer in under 20 seconds (referencing a number quoted by Gavin). If the bar for suitability is placed at taking only 1% of the block time (6 seconds) to upload one block to one peer, then 69% of the network fails for 20MB blocks. For comparison, only 10% fail this metric for 1MB blocks.\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e",
"sig": "2b287bd1f8732e6b75fbb5d41d4c7e6fbcc61c1f613a9f9304ffd1ac9041a0612aefb707f897221cf76972b602840ece648ebf0dac14805e84a60927587e6f0a"
}