[RndTbl] Shaw packet loss

Adam Thompson athompso at athompso.net
Tue Oct 19 11:03:31 CDT 2010

Mike, that sounds more like your gateway router running out of CPU cycles than Shaw doing traffic management.
I work with an ISP: doing the sort of thing you're describing *is* possible, but insanely difficult and expensive, especially on Shaw's scale.
I have a 2GHz router, it should handle it - I can test later this week.

-----Original Message-----
From: Mike Pfaiffer <high.res.mike at gmail.com>
Sender: roundtable-bounces at muug.mb.ca
Date: Tue, 19 Oct 2010 10:57:39 
To: Continuation of Round Table discussion<roundtable at muug.mb.ca>
Reply-To: Continuation of Round Table discussion <roundtable at muug.mb.ca>
Subject: Re: [RndTbl] Shaw packet loss

On 10-10-19 10:39 AM, Sean Walberg wrote:
> On Tue, Oct 19, 2010 at 10:36 AM, Mike Pfaiffer<high.res.mike at gmail.com>wrote:
>>         Then there is their policy of slowing down the entire connection if
>> they determine someone is using bittorrent on a LAN (even if the user
>> caps the up and down speeds)
> Do you have a source for this? Are you sure it's not because you're starving
> out your upstream and therefore not able to get ACKs out?
> Sean

	Give it a try. Grab a movie or something. Use a bittorrent client 
capable of capping the up and down speed. Ktorrent can do this. See what 
you can get for both up and down uncapped. Then try running say Firefox 
and look at its performance. Stop the bittorrent transfer and look at 
Firefox again in a few minutes. Set up a cap in bittorrent say 10K on 
both the up and down (bear in mind this is supposed to be a 
multi-megabit connection). Restart your bittorrent and see what happens 
with Firefox. You'll notice the bittorrent will transfer to what ever 
maximum you set while other programs will barely function on the 
internet. Local transfers on the LAN are fine though.


Roundtable mailing list
Roundtable at muug.mb.ca

More information about the Roundtable mailing list