📅 Original date posted:2011-08-05
🗒️ Summary of this message: The number of connections a node should use in Bitcoin is arbitrary; bandwidth is the relevant metric, and connections should be added until the bandwidth limit is reached.
📝 Original message:On 2011 August 05 Friday, Mike Hearn wrote:
> How many connections "should" a node use? We faced this decision in
> BitCoinJ recently and I asked the patch writer to reduce the number.
> It seems pretty arbitrary to me - if you aren't going to relay, a
> single connection should be good enough. Yes, it makes sybil easier,
> but if you pick the one node randomly enough it might be ok?
I don't really see that "number of connections" is the relevant metric. For a
well designed bit of software the number of connections shouldn't matter.
There's a bit of overhead in the operating system per connection, but I'd be
surprised if that ever became a limiting factor in a stateless system like
bitcoin. In fact, bitcoin would work perfectly well as a UDP system (I'm not
advocating that of course), and then there would be no such thing as a
connection.
Bandwidth is the measure that's relevant.
Therefore if bandwidth is the measure, just pick a bandwidth you like and
add/accept connections until you hit that bandwidth limit (probably averaged).
This has the advantage that it can be measured automatically, or sensibly set
by a user.
Andy
--
Dr Andy Parkins
andyparkins at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110805/4090edad/attachment.sig>;
Andy Parkins [ARCHIVE] /
npub1nx…7wjrv
2023-06-07 02:12:53
in reply to nevent1q…tqca
Author Public Key
npub1nxlvf9mj3jzgue25n5d9y47s3h5hvg0ded9hwpejdxj9mtrs34vs97wjrvSeen on
wss://relay.nostr.bandPublished at
2023-06-07 02:12:53Event JSON
{
"id": "74a49e30d614250b8197037d3476ccf5382ca63a7ed4b8d35cdf539d09927fa9",
"pubkey": "99bec497728c848e65549d1a5257d08de97621edcb4b77073269a45dac708d59",
"created_at": 1686103973,
"kind": 1,
"tags": [
[
"e",
"f7bac66510d148bc7cd5c36f79897fafe3410a2bc9df45238a65f8429b9407f0",
"",
"root"
],
[
"e",
"6d08ac61d77c0e48d688853275ea82f762ac9576566a44d5a60b63252db451bf",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "📅 Original date posted:2011-08-05\n🗒️ Summary of this message: The number of connections a node should use in Bitcoin is arbitrary; bandwidth is the relevant metric, and connections should be added until the bandwidth limit is reached.\n📝 Original message:On 2011 August 05 Friday, Mike Hearn wrote:\n\n\u003e How many connections \"should\" a node use? We faced this decision in\n\u003e BitCoinJ recently and I asked the patch writer to reduce the number.\n\u003e It seems pretty arbitrary to me - if you aren't going to relay, a\n\u003e single connection should be good enough. Yes, it makes sybil easier,\n\u003e but if you pick the one node randomly enough it might be ok?\n\nI don't really see that \"number of connections\" is the relevant metric. For a \nwell designed bit of software the number of connections shouldn't matter. \nThere's a bit of overhead in the operating system per connection, but I'd be \nsurprised if that ever became a limiting factor in a stateless system like \nbitcoin. In fact, bitcoin would work perfectly well as a UDP system (I'm not \nadvocating that of course), and then there would be no such thing as a \nconnection.\n\nBandwidth is the measure that's relevant.\n\nTherefore if bandwidth is the measure, just pick a bandwidth you like and \nadd/accept connections until you hit that bandwidth limit (probably averaged). \nThis has the advantage that it can be measured automatically, or sensibly set \nby a user.\n\n\nAndy\n\n-- \nDr Andy Parkins\nandyparkins at gmail.com\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 198 bytes\nDesc: This is a digitally signed message part.\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110805/4090edad/attachment.sig\u003e",
"sig": "527c4163848f338cad7d6798b7b86856deb499e8dbf572c2ac94ce665be278c7825b7466e8f41216baa295ccf774824958e88e25840fdd178c6e6e1cfdc30181"
}