This certainly would help out on a Gigabit LAN that's for sure. But won't really have any effect on folks interenet connections. 99% of all network cards out there now operate at 100Mbps or 1000Mbps. Your average internet connection isn't more than 1 or 2Mpbs. Of course there are you lucky bastages that live in a Metropolis areas that get some insanely fast internet connections. But nothing near 100Mbps or Gigabit
Now if you have a client that is running some bandwith intensive database applications on their LAN then this might just make a noticible difference. I would need to look into if this is a System Policy enabled on Server 2003 and Server 2000. If this is enabled on File Server's I'd be shocked...20% is a lot of overhead. 5% makes sense...but 20%?
QoS is important to make sure your packet stream is solid and reliable. TCP/IP by default is "best effort"...and UDP is "you get what you get" since the games that most people play use a mixture of both, QoS is really important to have on.
I typically reference MS support:
http://support.microsoft.com/default...;en-us;Q316666
Quote:
|
One hundred percent of the network bandwidth is available to be shared by all programs unless a program specifically requests priority bandwidth. This "reserved" bandwidth is still available to other programs unless the requesting program is sending data. By default, programs can reserve up to an aggregate bandwidth of 20 percent of the underlying link speed on each interface on an end computer. If the program that reserved the bandwidth is not sending sufficient data to use it, the unused part of the reserved bandwidth is available for other data flows on the same host.
|
That article even further states that claims of WinXP using only 20% of your available bandwidth due to QoS are false.