> On 7 May, 2020, at 10:58 am, Kevin Darbyshire-Bryant > <[email protected]> wrote: > > A curiosity has arisen: I use diffserv4 mode on a 20Mbit egress link. Bulk > tin has ‘capacity’ threshold of 1.2Mbit and because it’s a slow ’tin', the > default target & interval values get overridden to 14.6ms and 109.6ms > respectively. The 3 other tins are 5ms & 100ms defaults. > > I have a backup job that bulk uploads 5 simultaneous flows to Onedrive. The > sparse_delay, average_delay & peak_delay figures settle on 32, 38 & 43 ms > respectively with around 9 drops per second on that tin. > > I’m curious as to why the reported delays are over double the target latency?
It's likely that there's a minimum cwnd in your sender's TCP stack, which may be as large as 4 segments. In Linux it is 2 segments. No matter how much congestion signalling is asserted, the volume of data in flight (including retransmissions of dropped packets) will always correspond to at least that minimum per flow. If the path is short, most of that volume will exists in queues instead of on the wire. Fortunately, backups are unlikely to suffer from a small amount of extra latency, and Cake will isolate their influence from other flows that may be more sensitive. - Jonathan Morton _______________________________________________ Cake mailing list [email protected] https://lists.bufferbloat.net/listinfo/cake
