-
zigzag_8336 no offence, but bballad not only means corporate or school and home lan's he also means the WAN connection to your ISP.
I have explained this many times here on AO, and others did too, P2P sharing is due to the TCP/IP protocol and in combination with asynchronous lines a very inefficient method. four users can make a whole cable segment, could be 10 or 100 or even 1000 users drop to upload speeds. The thing is that without bandwidth management (like you can do with Unix / linux boxes) the upload from many p2p users (cause you need, without cheating, some upload in order to download) cable lines makes that the CMTS gets saturated. This upload saturation is not that difficult to reach since it's only something like 128k or 384k up on a 3Mbit down line. All ack packets are waiting to get through the continous upstream, so many packets from 'normal' webusers, gamers, ... got lost due to the saturation, this means also lag, your tcp/ip thinks: 'oohhh this is a bad connection' and your download speed drops to the speed it can establish a good connection -> this is going to be around... guess two times: 128k or 384k. This means you can lose approximately 368kB or 2.9Mbit in the case of 128k upload and 3Mbit download bandwidht. That's the reason why some admins do not like P2P ;)
Some networks have more then 3/4 of their traffic being useless crap.
-
Great explanation. This is why I take a *very* negative view of P2P. I worked for an ISP for a while, this was pre napster, but had I been there during Napster I would have supported the caps the owner insisted on ...Heck if I where running an ISP I would make it a violation of the terms of use to have a P2P server running.
Remember if you have a P2P server you are being very selfish and distroying the net connection of every one on the segment around you.
The only way I don't hae a probelm with someone useing P2P is if they are connected over dial up.
