At least on Win7 x64 with the 0.4.0-beta, I'm seeing in excess of 60^H^H70 simultaneous connections to/from the client.
This seems excessively high, for one. Additionally, there is no mechanism in the client itself to change the number, short of creating a bitcoin.conf (I limit my services wallets to 16 connections, already IMHO more than enough).
That is more a result of the bitcoin network not working well, it needs some serious examination, but so far (AFAIK) no one has stepped up to figure out why there are so many connections to any listening node.
Perhaps that's true. My suggestion, though, is to add a connection limit to the GUI client, with a reasonable default value.
On Fri, Nov 18, 2011 at 11:04 PM, Matt Corallo < reply@reply.github.com
wrote:
That is more a result of the bitcoin network not working well, it needs some serious examination, but so far (AFAIK) no one has stepped up to figure out why there are so many connections to any listening node.
Reply to this email directly or view it on GitHub: #643 (comment)
There is a limit - currently 100 IIRC, though I would vote for the option to change that in the GUI options menu. Setting it lower is something that would have to be thoroughly discussed first. As I mentioned, the network is already starved of nodes which accept incoming connections, limiting that number further could have very serious consequences. Someone needs to do some analysis of the network, but until then, the max connection limit really shouldnt be touched IMO.
Okay, that's a very legitimate concern. Personally I have a 40 Mbps+ cable modem connection and enable UPnP in order to serve the network. I can imagine lots of people, though, on much slower links, wondering why their available bandwidth dropped after installing Bitcoin.
And for nostalgia's sake, I'm also recalling those old limits built into consumer versions of MS Windows, like <= 100 TCP connections open at a time :P
On Sat, Nov 19, 2011 at 12:47 AM, Matt Corallo < reply@reply.github.com
wrote:
There is a limit - currently 100 IIRC, though I would vote for the option to change that in the GUI options menu. Setting it lower is something that would have to be thoroughly discussed first. As I mentioned, the network is already starved of nodes which accept incoming connections, limiting that number further could have very serious consequences. Someone needs to do some analysis of the network, but until then, the max connection limit really shouldnt be touched IMO.
Reply to this email directly or view it on GitHub: #643 (comment)
Use -maxconnections