Reviews:
 ·RoadRunner Cable
4 edits | reply to insomniac84
Re: They make no sense. Your describing a throttle by volume, which only slows p2p transfers making them last longer (IMO making the problem worse in the long term)
This new system will have to deal with the following situation:
User A is using p2p with some type of https transfer
User B is trying to pay his credit card bill online
How will it judge which packet is real https and which is not?
I doubt this will have any better results than sandive.
If they drive p2p to this expect millions of upset users who can't get a secure web page to work. |
|
patcat88
join:2002-04-05
Jamaica, NY
kudos:1 | said by DataRiker:Your describing a throttle by volume, which only slows p2p transfers making them last longer (IMO making the problem worse in the long term) This new system will have to deal with the following situation: User A is using p2p with some type of https transfer User B is trying to pay his credit card bill online How will it judge which packet is real https and which is not? I doubt this will have any better results than sandive. If they drive p2p to this expect millions of upset users who can't get a secure web page to work. Rolling 7 day window of GB usage. Top 10 percentile on the node get lowest priority until they fall out of top 10 percentile. If node is never saturated, then there are no problems with being lowest priority. |
|
Lazlow
join:2006-08-07
Saint Louis, MO | patcat88
That unfairly penalizes those who do the majority of their downloading during non peak hours(which does not cause congestion or cost the ISP anything extra). |
|
patcat88
join:2002-04-05
Jamaica, NY
kudos:1 | Whats downloading? 50% of your limit off peak, or 100% of your limit? Rolling window usage to assign priority levels is fair. If your node is not saturated, you have no reason to care.
What about the person who wants to torrent off peak, but not 24/7? are they to be placed in the same class as the person who torrents off peak 12/7/365?
Rolling window with percentile will separate the HTTS bill payer from the P2Per, without content discrimination.
The less you use, the higher your peak speed will be, and the more bursty it will be. If you want a circuit, your going to get treated like a circuit.
If you don't have a rolling window (much better than a powerboost bucket), how do you separate the user which will release the channel when they get their "task" done (download a 700mb movie via HTTP), vs a user that will NEVER release the channel and can never finish their "task" (a heavy P2P downloader, note most P2Pers eventually finish their downloads, their uploads are unstopable and unfinishable, but some P2Pers have a hoarding mentality and select to download 100s or 1000s of files and everything that shows up in the search, they never keep or watch or use everything they download). |
|
|
|
Lazlow
join:2006-08-07
Saint Louis, MO | The ONLY time that downloading causes congestion is during peak hours. I do 99% of my downloading between 11pm and 8am (off peak here). This causes no congestion and does not cost the ISP anything extra. However I do like to browse (here and other places). Under your formula my browsing would be "throttled" because of my off peak downloading(which is causing a problem for no one). This is why a monthly or even daily download limit does not work. What needs to be done is to only count the usage during peak congestion. I can easily download(off peak ) 500GB+/month without contributing to the congestion while another person can download less than 150GB/month(1hr/night during peak congestion) and cause lots of congestion.
A pure proticol agnostic throttle during peak hours(only) is (in the short term) a good answer(which is what Comcast is using right now). The problem with this system is that there is the risk the ISPs will use it (long term) as an excuse not to upgrade their systems. |
|
1 edit | reply to DataRiker
said by DataRiker:This new system will have to deal with the following situation: User A is using p2p with some type of https transfer User B is trying to pay his credit card bill online How will it judge which packet is real https and which is not? That https p2p is going to make many connections to different hosts and not just one connection. And it will try to transfer much more data. Depending on how good you detect it, it might get a few seconds of max speed, then you start to throttle it back. |
|
