This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
qos [2014/07/01 13:42] pbix [ACC keeps lowering my link limit] |
qos [2017/12/29 01:21] (current) ispyisail [Router Performance] |
||
---|---|---|---|
Line 19: | Line 19: | ||
How about an analogy? I fly a lot and if you do too then you understand that when it’s time to board the airplane we do not just all rush at the door. The gate agent enforces the airline’s quality of service plan for each passenger. She starts by boarding handicapped folks, then we move onto the airline’s diamond members, then gold, silver and finally we arrive at the bulk class. In this analogy the gate agent is the router and the passengers are the packets of data trying to get through to the WAN. The point is that for | How about an analogy? I fly a lot and if you do too then you understand that when it’s time to board the airplane we do not just all rush at the door. The gate agent enforces the airline’s quality of service plan for each passenger. She starts by boarding handicapped folks, then we move onto the airline’s diamond members, then gold, silver and finally we arrive at the bulk class. In this analogy the gate agent is the router and the passengers are the packets of data trying to get through to the WAN. The point is that for | ||
- | those diamond members to experience high quality the average Joes must wait. One more interesting lesson from this example is that if there is no one else waiting to board the plane when you show up it does not matter what your status is, you get to board next. The lesson here is that if the WAN is not | + | those diamond members to experience high quality the average Joes must wait. When people are waiting to board we call this the ' |
saturated your QoS setup will not matter much, all packets get immediately transmitted. | saturated your QoS setup will not matter much, all packets get immediately transmitted. | ||
Line 212: | Line 212: | ||
==== Total Bandwidth Field ==== | ==== Total Bandwidth Field ==== | ||
- | Below the class table is the total (upload/ | + | Below the class table is the total (upload/ |
- | critical | + | |
- | congestion controller or not and if your WAN connection type (set on the Connection-> | + | |
- | to PPPoE. Assuming | + | |
- | When using PPPoE you should consult | + | Now start with the upload |
- | is running at. Enter the uplink/ | + | |
- | When not using PPPoE you should | + | On the download page the value you enter depends on if you are using ACC or not. When using ACC you enter the maximum download speed you saw. If you enter a value even 10% higher its OK too. ACC is going to automatically adjust |
- | 95% of your measured upload speed on the upload screen. The way I recommend to measure | + | |
- | speed is to first turn QoS off, then make sure no one is using the WAN link and then run a speed test such | + | |
- | as the one http:// | + | |
- | If you are not using the ACC then you will generally | + | If you are not using ACC then things get more complicated. |
- | values mentioned above. The amount to reduce varies from 20-80% | + | |
- | your ISP. For this reason I recommend that you use the ACC. | + | |
===== Active Congestion Controller (ACC) ===== | ===== Active Congestion Controller (ACC) ===== | ||
Line 259: | Line 250: | ||
own this setting can be used to remedy the problem. This value will normally be between 40-90ms and | own this setting can be used to remedy the problem. This value will normally be between 40-90ms and | ||
can be observed when the ACC is in MINRTT mode as the ping time limit. | can be observed when the ACC is in MINRTT mode as the ping time limit. | ||
+ | |||
+ | ===== Router Performance ===== | ||
+ | |||
+ | Your router has a CPU and that CPU has a limit on how much data is can process per second. | ||
+ | |||
+ | This will happen somewhere between 10Mbps and 500Mbps depending on your router and what Gargoyle features you are using. | ||
+ | |||
+ | Bandwidth monitoring and QoS are the two features that take the most processing for your router. | ||
+ | |||
+ | Don't complain on the forum that your router' | ||
+ | |||
+ | ---------------- | ||
+ | |||
+ | All routers have a maximum processing speed for the WAN link. If you lower your total WAN bandwidth (upload plus download) to below this maximum on the Gargoyle QoS screens then Gargoyle will throttle your throughput and all your Gargoyle functions will work properly. This may result in you not being able to utilize the full bandwidth your ISP provides you but you will have stable and predictable performance. | ||
+ | |||
+ | Selecting a router that has enough horsepower to handle your full bandwidth is important if you really want to use all your available bandwidth. Stock firmware which comes with your modem will usually provide higher throughput than Gargoyle. The reason for this is simple. The stock firmware does not have the advanced features of Gargoyle. Especially QoS and Bandwidth monitoring. These are the features that require CPU horsepower. If you turn them off in Gargoyle you will also see a high throughput capability. | ||
+ | |||
+ | Like a car top-end speed is not the only desirable feature. The many other features that you use everyday are usually what you should concentrate on and these are what Gargoyle provides. | ||
===== FAQS ===== | ===== FAQS ===== |