#17807: qos codel patch noecn to eth1 (wan) and qos-scripts question
-------------------------+------------------------
Reporter: robnitro@… | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone:
Component: packages | Version: Trunk
Resolution: | Keywords:
-------------------------+------------------------
Comment (by dtaht):
Gah, I missed a question. The prospect of changing the flows variable is
that at very low values (say, 16 or 32), the AQM portion of the code
dominates. (at flows "1", it degrades to pure codel). At the higher
values, for edge devices, the "fq" portion of the code dominates. We did a
bunch of simulation and tests, put a finger in the wind and decided that
1024 queues was "enough" for up to gigE along the edge for everything we
looked at. There is some thinking that a larger number of flows makes
sense for servers running at that speed and at 10GigE, but those ideas are
still baking in the new "fq" and pacing code at google, and if you are
building a 10GigE openwrt router, please come talk to me about the rangely
processor. :)
And I forgot that "debloat" at least used to, trim the wifi aggregation
queue length down to reasonable values for typical bandwidths (instead of)
STA right next to the AP bandwidths. Depending on what you commit you
pulled,
We had changed it back to the default queue length after 5 months of
battling with bufferbloat.net bug 442, which I am deeply grateful to felix
for finding and fixing. Reducing the aggregation buffer size to 12 for BE,
BK, and VO was often helpful for multistation access (it's still the wrong
answer long term, but feel free to try it)
--
Ticket URL: <https://dev.openwrt.org/ticket/17807#comment:11>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
