You can't use codel for the qos in gargoyle, but hsfc/ sfq is much better because like mentioned, you can use caps.
sqm_scripts was not too good in balancing out load- like torrents would still saturate the connection because of many multiple connections!
But you can change the eth0 eth1 wlan1 wlan0 to use fq_codel which helps with the internal delays, especially good for wireless. I'm using my own customized settings that I have learned work best for me when I used openwrt qos and sqm. In fact, fq_codel itself on the device can reduce ping spikes if your line is slower than you put for limits in gargoyle.
robnitro wrote:You can't use codel for the qos in gargoyle, but hsfc/ sfq is much better because like mentioned, you can use caps.
sqm_scripts was not too good in balancing out load- like torrents would still saturate the connection because of many multiple connections!
But you can change the eth0 eth1 wlan1 wlan0 to use fq_codel which helps with the internal delays, especially good for wireless. I'm using my own customized settings that I have learned work best for me when I used openwrt qos and sqm. In fact, fq_codel itself on the device can reduce ping spikes if your line is slower than you put for limits in gargoyle.
It gives a codel queue for the interfaces themselves, not touching the QOS queues.
My friend has 150 mbit fiber, so he doesn't use qos. But if he leaves stock queues (fifo?) he can get spikes to 200 ms. With codel, the latency never goes above 120ms. It's just smarter about how it handles traffic, even when you don't use qos.
I see that the newer 1.7.1 does fq_codel by default on eth0 and eth1 (lan and wan). But still wlan (wireless) is not using it.
Just to explain the basics of codel and why I selected those values.
Limit is the number of packets it will hold onto in the queue. A lower value would mean less max speed, but less delay. (best value that I found helps without qos- set it lower on the outgoing interface and latency doesn't spike high!)
Quantum is the size of the packets it will split into for prioritization. (I didn't see much difference in testing but 300-500 is normally ok)
Target is where the queue wants to have max delay- I didn't see any benefit between stock and my setting of 2ms.
Interval is just how often the queue re-analyzes delays to adjust for latency.
pbix wrote:
People who want to try fq_codel in Gargoyle can replace their /etc/init.d/qos_gargoyle.sh scripts with the attached. I will be watching for any comments.
I just replaced qos_gargoyle and enabled QoS but tc -d qdisc still shows pfifo_fast not fq_codel, what do?