Who is running the Mother of All Gargoyle Deployments?
Posted: Tue Aug 28, 2012 11:11 am
I'm running NetEqualizer in a 262-room hotel setting right now.
I just deployed a Gargoyle on TP-Link 1043ND to a bar/restaurant with 12Mbit and 40 concurrent users. Not so many users; loads are under control. Circuit is infrequently maxed out. Processor loads negligible.
At a 262-room hotel though, they max out their 15Mbit much of the time. Even with individual user Connection Limits set at 40. This is with NetEq Lite, which keeps priority traffic humming smoothly. But its processor loads have been an issue.
Question: How many users are you handling with your Gargoyle? How many megabit? What kind of processor loads are you seeing? Who is using Gargoyle for multi-tenant applications, and how big are we talking?
Who's got over 100 users and maxing out 25 megabit or more?
Interestingly, the sort of "net abuse" we see at hotel is not high connection-count torrent traffic, typically hundreds of UDP connections. Rather, it's two or three connections per user of high-rate HTTP TCP traffic. Rapidshare and the like.
Note: such "network hog" activity is actually just modern entertainment choice for a hotel guest. They know the Internet has more interesting viewing fodder than cable TV as well as we do. So not all of this "network hogging" is a bad thing for paying guests.
So really, setting HTTP as a priority class will "prioritize" these type of "hog" downloads. Equality will be ensured through the division of class capacity. Does that provide enough fairness for your users? Still I am mostly interested in Who is running the Mother of All Gargoyle Deployments?
I just deployed a Gargoyle on TP-Link 1043ND to a bar/restaurant with 12Mbit and 40 concurrent users. Not so many users; loads are under control. Circuit is infrequently maxed out. Processor loads negligible.
At a 262-room hotel though, they max out their 15Mbit much of the time. Even with individual user Connection Limits set at 40. This is with NetEq Lite, which keeps priority traffic humming smoothly. But its processor loads have been an issue.
Question: How many users are you handling with your Gargoyle? How many megabit? What kind of processor loads are you seeing? Who is using Gargoyle for multi-tenant applications, and how big are we talking?
Who's got over 100 users and maxing out 25 megabit or more?
Interestingly, the sort of "net abuse" we see at hotel is not high connection-count torrent traffic, typically hundreds of UDP connections. Rather, it's two or three connections per user of high-rate HTTP TCP traffic. Rapidshare and the like.
Note: such "network hog" activity is actually just modern entertainment choice for a hotel guest. They know the Internet has more interesting viewing fodder than cable TV as well as we do. So not all of this "network hogging" is a bad thing for paying guests.
So really, setting HTTP as a priority class will "prioritize" these type of "hog" downloads. Equality will be ensured through the division of class capacity. Does that provide enough fairness for your users? Still I am mostly interested in Who is running the Mother of All Gargoyle Deployments?