 StewyPremium
join:2007-12-12
Kitchener, ON | reply to FFFF
Re: Throttling will continue with Rogers' new usage plans All I've been personally battling the question of WHY throttle lately, I kinda understood when there were no caps but now with caps in place I need a logical answer to this question.
I was hesitant to post this but here goes since this seems to be the main topic of this thread.
Question 1) If Rogers caps the bandwidth use to your max, for ex. extreme to 95 Gigs, why is there a need to throttle P2P application since whether I use P2P HTTP or NNTP or any other protocol I will still use 95 Gigs anyway. On top of that I can max out my connection 24/7 with HTTP or NNTP, how can those two not affect traffic but P2P can ?
Question 2) If Rogers would charge your account "Tiered Service Bandwidth" for excess bandwidth use, why is there a need to implement throttling ? Would they not make a killing by selling you all that extra P2P bandwidth ?
Question 3) Why can any user on any given day on NNTP or HTTP download over 200Gig/day and over 1 Terabyte per week with no problems and only pay $25 max per month extra. However you can't download your cap with P2P which seems to be a network burden. If P2P is such a network burden, then why is downloading 2 or 4 Terabites of NNTP not a burden and is not being throttled ?
Question 4) If network management or "load" is the issue, why is there a need to throttle 24/7 and even on weekends? is the network being used to the max at 5AM Sunday mornings?
Question 5) How can small 3rd party ISP's be able to offer un-throttled access without affecting their network and with room to spare when two of the biggest ISP's in the country can't.
Can someone please explain to me once and for all how P2P can be such a bandwidth burden but not HTTP or NNTP.
I would like to have a logical and technical reason to throttle but right now the only possible conclusion that I can come up with is that the Throttling of P2P is a type of punishment for P2P cutting into the Cable and Telco's media business. |
 sbrookPremium,Mod
join:2001-12-14
Ottawa
kudos:4
 ·TekSavvy Cable
·Rogers Hi-Speed
| This issue applies only to cable modems ...
Cable is a shared medium, particularly for its upstream. There is bandwidth available for only so many simultaneous upstream data paths on a given cable segment. The CMTS (Cable modem termination system - essentially the modem and controller at the cable head end) control when modems can transmit on your cable segment.
When your modem has data to transmit, it must do so by taking part in a bidding war. The CMTS says "Transmit on frequency X in time slot NN" There are only so many available time slots and frequencies available. The bidding war is a freeforall in another time slot. If your modem doesn't get assigned a slot in the current bidding time slot, it has to wait for the next and bid in that one. The bidding process is kind of like the old manual people on the floor type stock exchange!
So the upstream is very limited. BitTorrents are not just download, they rely on your uploading to others. Torrent users leave their torrents running for prolonged periods, and the torrents present a constant upstream traffic demand. The result is that very few torrent users on a cable segment can degrade performance for all users on the segment because they fill the available upstream slots very quickly.
Throttling was introduced to a) slow the upstream demand (which is why it's a 24/7 thing unlike Bell's peak demand only) and b) to cheese off users to the point where they don't really want to use it!
So, throttling on a cable network has nothing to do with the amount of transit bandwidth the ISP is consuming (which is what caps aim to control). |
