Re: [Cake] 5ms target hurting tcp throughput tweakable?

2017-03-01 Thread Andy Furniss
Benjamin Cronce wrote: I have not sampled YouTube data in a while, but the last time I looked it had packet-pacing issues. With TCP going from idle to full, several times a second. Not only do you get the issue that TCP will front-load the entire TCP window all at once, but if the data being tra

Re: [Cake] 5ms target hurting tcp throughput tweakable?

2017-02-28 Thread Benjamin Cronce
On Mon, Feb 27, 2017 at 1:26 PM, Andy Furniss wrote: > Sebastian Moeller wrote: > >> Hi Andy, >> >> >> On Feb 27, 2017, at 19:02, Andy Furniss >>> wrote: >>> >>> Sebastian Moeller wrote: >>> Looking at tc-adv, I would recommend to use “rtt 50” (maybe it is “rtt 50ms”) which allows to d

Re: [Cake] 5ms target hurting tcp throughput tweakable?

2017-02-27 Thread Andy Furniss
Sebastian Moeller wrote: Hi Andy, On Feb 27, 2017, at 19:02, Andy Furniss wrote: Sebastian Moeller wrote: Looking at tc-adv, I would recommend to use “rtt 50” (maybe it is “rtt 50ms”) which allows to directly explicitly request a new “interval” (which IIRC is corresponding to the time you a

Re: [Cake] 5ms target hurting tcp throughput tweakable?

2017-02-27 Thread Sebastian Moeller
Hi Andy, > On Feb 27, 2017, at 19:02, Andy Furniss wrote: > > Sebastian Moeller wrote: >> Looking at tc-adv, I would recommend to use “rtt 50” (maybe it is >> “rtt 50ms”) which allows to directly explicitly request a new >> “interval” (which IIRC is corresponding to the time you allow for >> th

Re: [Cake] 5ms target hurting tcp throughput tweakable?

2017-02-27 Thread Andy Furniss
Sebastian Moeller wrote: Looking at tc-adv, I would recommend to use “rtt 50” (maybe it is “rtt 50ms”) which allows to directly explicitly request a new “interval” (which IIRC is corresponding to the time you allow for the TCP control loop to react to cake’s ecn-marking/dropping) “target’ will be

Re: [Cake] 5ms target hurting tcp throughput tweakable?

2017-02-26 Thread Sebastian Moeller
Looking at tc-adv, I would recommend to use “rtt 50” (maybe it is “rtt 50ms”) which allows to directly explicitly request a new “interval” (which IIRC is corresponding to the time you allow for the TCP control loop to react to cake’s ecn-marking/dropping) “target’ will be calculated as 5% of the

Re: [Cake] 5ms target hurting tcp throughput tweakable?

2017-02-26 Thread Andy Furniss
Jonathan Morton wrote: On 26 Feb, 2017, at 15:16, Andy Furniss wrote: Is there any way or plans to allow users to relax slightly the target? You can do that by selecting a higher assumed RTT, for instance with the “oceanic” or “satellite” keywords. This also increases the interval, which

Re: [Cake] 5ms target hurting tcp throughput tweakable?

2017-02-26 Thread Jonathan Morton
> On 26 Feb, 2017, at 15:16, Andy Furniss wrote: > > Is there any way or plans to allow users to relax slightly the target? You can do that by selecting a higher assumed RTT, for instance with the “oceanic” or “satellite” keywords. This also increases the interval, which makes the AQM less a

[Cake] 5ms target hurting tcp throughput tweakable?

2017-02-26 Thread Andy Furniss
Hi, I am new to cake and just messing around currently. I notice that on my setup with vdsl2 20mbit sync the default 5ms target on best effort hurts netperf throughput a bit as latency to host rises. My setup. tc qdisc add dev ppp0 handle 1:0 root cake bandwidth 19690kbit raw overhead 34 diffs