One thing the original sqm-scripts did (with fq_codel) was explicitly
deprioritize ping with a filter.
I had written in my original "wondershaper must die" rant how stupid
it was to prioritize ping upwards to "impress your friends" - as that
was the case in many, many a wshaper implementation I'
Okay, I think I’ve worked out what is happening.
At 250KB/s, it takes 6ms to get one 1500-byte bulk packet down the pipe. This
is unavoidable, so having a bulk flow competing with your game traffic will
always increase your peak latency by that much.
With three independent game streams in play
Jonathan Morton wrote:
On 4 Mar, 2017, at 20:21, Andy Furniss wrote:
So I mark icmp as ef which does go to voice and repeat the test.
It performs slightly worse for max delay.
Hmm.
If I’m reading those fping commands right, you’re sending a total of 36KB/s in
ICMP (4x 60pps 150B), which
> On 4 Mar, 2017, at 20:21, Andy Furniss wrote:
>
> So I mark icmp as ef which does go to voice and repeat the test.
>
> It performs slightly worse for max delay.
Hmm.
If I’m reading those fping commands right, you’re sending a total of 36KB/s in
ICMP (4x 60pps 150B), which should fit into t
In the UK quite a lot of people have a 40/2 vdsl2 product.
Thankfully not me, ugh, it doesn't even have enough bandwidth for
sack per incoming in recovery - but "pretending" I wanted to see what
cake was like.
tc qdisc add dev enp6s0 handle 1:0 root cake bandwidth 1969230bit
overhead 34 dual-sr
Andy Furniss wrote:
Next test = use vanilla git iproute2, even worse = Oops. So may be
best to avoid that one for now :-).
I manages to avoid the Oops by udating iptables from 1.6.0 to 1.6.1
which is handy, though now it fails with an error from iptables - but
at least it fails without taking
