I missed the case of ack mostly traffic, which as it has a 20x1 ratio vs
big packets, requires that the queues be
much larger. On an ACK-heavy load, at high bandwidths, we end up with
fq_codel in an “interesting” drop tail state, where it still admits
packets but ends up optimizing for “new” flows that aren’t actually
“new”.
I do not know the right values. The fq_codel default of 10k packets is sufficient to run the router out of memory in a variety of scenarios, resulting in a crash.
Usually I have a test box and not netperf running on the other side of the router.
Figuring out what those bandwidths actually are and the interrelationship between the device queuing, EDCA, and fq_codel is going to be the subject of a long month or three. Or longer.
I may well have an interaction with netperf running on the box too.