bradlesliect
Senior Member
- Joined
- Nov 13, 2006
- Messages
- 518
- Reaction score
- 0
So to summarize:
The QoS tables need to be tweaked or the heavy users need to be outright throttled.
Hypothetically, if users were throttled for heavy usage and were told the cap was 100Gb, how would that fix things? Its not like you will be changing your usage habits to only attempt to consume 100Gb per month, then you could just as well buy a capped unshaped account which would amount to the same thing.
I remember when our highsite QoS tables were terrible on WUG and killed downloads for some users, few tweaks fixed it, for a while, until another group who had been used to their speeds, started complaining that their speeds were now dropping (due to the bandwidth now being more evenly shared)
For interest sake
If EVERY subscriber were to receive all content CONSTANTLY on their line speeds ALL THE TIME, how much bandwidth would AH need to have access to to cater for that
I like your analogy, however, we used have a look at our network, see where the highest amount of traffic is coming from causing congestion and affecting all users, apply a packet sniffer and then apply and access-list and/or QoS to that entry to our network.
This worked because the congestion decreased, the culprits were found, the TPOC contacted and advised of our AUP and its consequences letting the TPOC know the account is being monitored and everything was just HUNKY DORY! Also...doing trend analysis we would see which times of the day there was a sudden peak and where its coming from. Most evenings and weekends Fri - Sat) we would remove the access-list and/or QoS restriction allowing the serious surfers some room.
Whenever this was applied a notice would be posted to the effect of "we are experiencing network congestion and are atending" and the customer is happy and notice is resolved when traffic subsides again. Keeping the customer informed is key! Lately I notice there is a lack thereof?
After all, I mean nowadays most users setup download managers, start them up and night, go to bed, check them in the morning and sometimes let them run even though it might be a bit slow because everyone needs connectivity.
Protocol Priority List:
1. HTTP - including DL via HTTP
2. Mail
3. FTP
4. Streaming
5. P2P
I know the above worked with companies with leased lines and ADSL connections - with Static IP Pools - but with the technology and packet sniffers available, surely this can be done too? Afterall, all services need to be made viable for the business and provide the customer with a "warm and fuzzy" feeling.

