* Re: [Bloat] Curious case of local "Fiber"
2018-02-12 13:56 ` Jonathan Morton
@ 2018-02-12 14:01 ` Neal Cardwell
2018-02-12 14:34 ` Jim Gettys
1 sibling, 0 replies; 4+ messages in thread
From: Neal Cardwell @ 2018-02-12 14:01 UTC (permalink / raw)
To: Jonathan Morton; +Cc: Bruno George Moraes, bloat
[-- Attachment #1: Type: text/plain, Size: 632 bytes --]
On Mon, Feb 12, 2018 at 8:56 AM, Jonathan Morton <chromatix99@gmail.com>
wrote:
> > On 22 Jan, 2018, at 10:07 pm, Bruno George Moraes <brunogm0@gmail.com>
> wrote:
> >
> > My NIC is configured to only 1/1 buffers, then MTU 1492 (increased of
> default 1480), PPoE login with Windows 10 using CUBIC.
>
> I didn't know Windows supported CUBIC. The default AFAIK is Compound TCP,
> if it isn't NewReno.
>
FWIW, I believe some recent versions of Windows 10 can be optionally
configured to use CUBIC:
https://blogs.technet.microsoft.com/networking/2017/07/13/core-network-stack-features-in-the-creators-update-for-windows-10/
neal
[-- Attachment #2: Type: text/html, Size: 1266 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Bloat] Curious case of local "Fiber"
2018-02-12 13:56 ` Jonathan Morton
2018-02-12 14:01 ` Neal Cardwell
@ 2018-02-12 14:34 ` Jim Gettys
1 sibling, 0 replies; 4+ messages in thread
From: Jim Gettys @ 2018-02-12 14:34 UTC (permalink / raw)
To: Jonathan Morton; +Cc: Bruno George Moraes, bloat
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
On Mon, Feb 12, 2018 at 8:56 AM, Jonathan Morton <chromatix99@gmail.com>
wrote:
> > On 22 Jan, 2018, at 10:07 pm, Bruno George Moraes <brunogm0@gmail.com>
> wrote:
> >
> > My NIC is configured to only 1/1 buffers, then MTU 1492 (increased of
> default 1480), PPoE login with Windows 10 using CUBIC.
>
> I didn't know Windows supported CUBIC. The default AFAIK is Compound TCP,
> if it isn't NewReno.
>
> In any case, it looks like the bottleneck isn't at your NIC (so your
> settings don't matter), but at the router terminating the fibre for the
> whole building. That's the best place to mitigate the bloat, since it
> would work for the whole building's uplinks.
>
Note, as always, you should locate your bottleneck.
WiFi is also highly suspect; you have terrible bloat in the upload
direction, which is probably typical for a WiFi bottleneck from a
device/laptop.
- Jim
>
> - Jonathan Morton
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 2255 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread