Best way to increase max global connections limit in sp2?

[0roo0roo]

..

 

[Sunner]

No it doesn't.

 

[sswingle]

This was hard

http://www.google.com/search?s...&q=max+connections+sp2

 

[KenAF2]

Keep in mind you need to reapply the patch every time Microsoft patches TCPIP.SYS (to fix a bug), which overwrites the connections change. Microsoft has done this two or three times in the past six months, the most recently about six weeks ago. If you haven't applied the connections patch since, then you no longer have it.

 

[LuDaCriS66]

There is no connection limit. The limit is on connection attempts per second. It doesn't hamper p2p performance in terms of many connections you can get

 

[KenAF2]

Originally posted by: LuDaCriS66
There is no connection limit. The limit is on connection attempts per second. It doesn't hamper p2p performance in terms of many connections you can get

It's the number of half-open TCP connections per second waiting for a reply.

The default is five for XP Home, ten for XP Pro, ten for Vista Business / Home Premium, and fifteen for Vista Ultimate.

If you are downloading a p2p file with a lot of peers/seeds, your system can only open and poll 10 connections per second, and some of them won't respond, due to the fact that not everyone correctly opens their ports. At any given second, only five of those ten attempted connections might actually result in return data. Hence, it takes longer time to connect to more peers and download at full speed.

So you are right that it doesn't hamper p2p throughput or your total number of connections, but it does potentially lengthen the amount of time it takes for you to reach full p2p throughput.

This is easily verifiable in XP Pro. Change your connection limit from the default of 10 to 5. Time how long it takes for you to reach 100 peers. Now change your connection limit to 50 and time how long it takes you to reach 100 peers.

 

[nweaver]

Originally posted by: KenAF2

Originally posted by: LuDaCriS66
There is no connection limit. The limit is on connection attempts per second. It doesn't hamper p2p performance in terms of many connections you can get

It's the number of half-open TCP connections per second waiting for a reply.

The default is five for XP Home, ten for XP Pro, ten for Vista Business / Home Premium, and fifteen for Vista Ultimate.

If you are downloading a p2p file with a lot of peers/seeds, your system can only open and poll 10 connections per second, and some of them won't respond, due to the fact that not everyone correctly opens their ports. At any given second, only five of those ten attempted connections might actually result in return data. Hence, it takes longer time to connect to more peers and download at full speed.

So you are right that it doesn't hamper p2p throughput or your total number of connections, but it does potentially lengthen the amount of time it takes for you to reach full p2p throughput.

This is easily verifiable in XP Pro. Change your connection limit from the default of 10 to 5. Time how long it takes for you to reach 100 peers. Now change your connection limit to 50 and time how long it takes you to reach 100 peers.

eh...are you sure you are not thinking of Samba connections: I know that Home is limited to 5 concurrent SMB connections, pro is 10, not sure on what Vista's limits are.


Even with default (assuming you are right) it just means it will take a little longer to start, but not much.