Could anyone post up the solution to Sp2 and download speeds?

[imported_Skorpio]

Anyone got a link? to increasing download speeds?....tried to do a search..cant find it

 

[n0cmonkey]

Gigabit ethernet?

What "speed limiter" are you talking about?

 

[earthling30]

Originally posted by: n0cmonkey
Gigabit ethernet?

What "speed limiter" are you talking about?

I'm not sure about him but after the SP2 update on two PCs and fresh install on 2 PCs it has slowed my download speed from 250 KB/s to 40-60 KB/s. That maybe what Skorpio is refering to.

 

[earthling30]

Originally posted by: Skorpio
Anyone got a link? to increasing download speeds?....tried to do a search..cant find it

Skorpio, I'm currently working with M$ to resolve this issue (that is if you're having the same problem I'm having), once I find something that works I'll let you all know the results and what it took to fix the problem.

 

[n0cmonkey]

Originally posted by: earthling30

Originally posted by: n0cmonkey
Gigabit ethernet?

What "speed limiter" are you talking about?

I'm not sure about him but after the SP2 update on two PCs and fresh install on 2 PCs it has slowed my download speed from 250 KB/s to 40-60 KB/s. That maybe what Skorpio is refering to.

Could it be the queueing stuff bsobel or Smilin (sorry, can't remember who, probably both) mentioned in another thread?

Off to search.

 

[n0cmonkey]

In this thread bsobel explains the queue pretty well, although there was no mention of the exact procedure to turn it off. It deals with the registry though, so I'm not going to search for it (I hate editing the registry, and don't want to link to a broken article).

Repeating misinformation does not make it true. There is NOT a new TCP/IP connection limit in SP2. What has changed is a queue (not a limit) for unestablished new connections. This *in no way* puts a cap on the number of connections that can be established at one time. The effect of the change is that port scanners and flash worms will propigate slower (as they tend to hit lots of addresses where the tcp handshake will not complete). You can turn the behaviour off via a registry change if you need to (say) run a portscanner for valid reasons.

and

The people claiming that their is a TCP/IP connection limit in SP2 are spreading FUD (this isn't directed at you elkinm, I'll explain what MS did in a second). I've seen this 'limit' quoted on a zillion sites, and it simply not true.

What was added was a queue (not a limit) of the number of uncompleted TCP connection outstanding. The default queue size is 10. Which means you can attempt to establish 10 TCP connection at once and their is no change in the behaviour. If you try to establish 20 at once, the first 10 are put on the wire while the next 10 are queued and released as those first 10 either complete or fail (e.g. first connection is built, #11 is put on the wire, #4 fails, #12 is put on the wire, and so on).

In 'normal' usage, TCP connection establish quickly and you simply won't notice any difference. Where you will see a difference is if you try to create a large number of connections to sites which are not listening/responding to your requests (so in your examples "Multiple IE or other active browsers, multiple downloads, multiple email, telnet, ftp, ssh clients and others may run. Norton update, weatherbug, VPN, terminal services, and a telnet and web server on my PC, and possibly multiple multisource download clients and programs, by own or something like steam or fileplanet." there are all services which will respond quickly and even if you tried really hard, I do not believe you would ever be able to determine if the queuing happened.)

So, why the change? Flash worms that utilize TCP connections typically sit and loop while connecting to a random IP (they then attempt to infect that machine and they go back to picking another random target). Some of these worms can literally eat up your entire connection while they sit and pump packets out, since many of the destinations are not going to be valid targets (since the selection was random) this queue will kick in and help throttle how quickly the worm can leave the box.

Even throttled the worm will still spread quickly, but more importantly (and the reason for this feature), your connection will not become so unusable that you will be unable to access updates/repair tools/patches/etc.

Bill

No doubt he'll be along later to help out more if this is way off base.

 

[sunase]

wow, that person must not be a native english speaker. he goes nuts saying it's not a limit and then says it's limited to working on ten incomplete at once whereas before it could do many at once. Oo complete contradiction.

it doesn't matter if they aren't lost, it's still a limit and it does slow down p2p downloads that need to make and break many connections (downloading many parts of many different files from many clients).

edit: spelling, lol

 

[imported_Skorpio]

Cool, thx guys for replying, I just needed the explaniaton by Bill about the queueing stuff /tcp/ip connection limit by Bsobel.

 

[kylef]

Please try to be a *little* bit more specific when you're describing your problems before assuming that the behavior you see is a result of any one culprit.

What apps are you using to download? What are you downloading?

Asking why your downloads are so slow is like asking "Why does my computer take so long to boot" without describing any more details.

There is no bandwidth cap or "speed limiter" in Sp2. If the app performing the download makes more than 10 simultaneous TCP connections, then you MIGHT be experiencing an overall throughput drop resulting from the new queue. So it depends heavily on the app you are using.