Date: Mon, 30 Jan 2023 18:30:00 -0500 From: Matt Garber <matt.garber@gmail.com> To: freebsd-stable@freebsd.org Subject: Re: Slow WAN traffic to FreeBSD hosts but not to Linux hosts---how to debug/fix? Message-ID: <CANwXMPNBkWQHzT4f%2Bjy0RV1gK7R6nJOWYsG5NZTf9RadRDNfXg@mail.gmail.com> In-Reply-To: <tr9g44$d3l$1@ciao.gmane.io> References: <95EDCFCA-7E3F-458F-85A6-856D606B9D98@gromit.dlib.vt.edu> <tr9g44$d3l$1@ciao.gmane.io>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000b0f07f05f38398b8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > > Any help/insight is gratefully appreciated. > > > > Cheers, > > > > Paul. > > > > sysctl net.inet.tcp.cc.algorithm=3Dhtcp > > I would set "htcp" on the server and home computer to improve through in > your type of situation. There may be other FreeBSD sysctls that have bad defaults in this scenario and could be better tuned, but I doubt changing the CC algorithm at this point is the problem =E2=80=94 at least not so much a problem that=E2=80=99= s causing throughput to be reduced so drastically. Happy to be wrong if that does help things quickly and easily, though. (Since OP mentioned that FreeBSD CC was set to CUBIC, that would match what the Linux boxes are using by default, too, unless they=E2=80=99ve been chan= ged to something newer like BBR=E2=80=A6 so seems like CUBIC *should* be performin= g fine on this WAN link, and the difference is something else.) =E2=80=94Matt --000000000000b0f07f05f38398b8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div><div><div><br></div><div dir=3D"auto"><div class=3D"gmail_quote"></div= ></div></div><div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px= 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;b= order-left-color:rgb(204,204,204)"> > Any help/insight is gratefully appreciated.<br> > <br> > Cheers,<br> > <br> > Paul.<br> > <br> <br> sysctl net.inet.tcp.cc.algorithm=3Dhtcp<br> <br> I would set "htcp" on the server and home computer to improve thr= ough in <br> your type of situation.</blockquote><div dir=3D"auto"><br></div><div dir=3D= "auto"><br></div></div></div><div><div><div dir=3D"auto">There may be other= FreeBSD sysctls that have bad defaults in this scenario and could be bette= r tuned, but I doubt changing the CC algorithm at this point is the problem= =E2=80=94 at least not so much a problem that=E2=80=99s causing throughput= to be reduced so drastically. Happy to be wrong if that does help things q= uickly and easily, though.</div><div dir=3D"auto"><br></div><div dir=3D"aut= o">(Since OP mentioned that FreeBSD CC was set to CUBIC, that would match w= hat the Linux boxes are using by default, too, unless they=E2=80=99ve been = changed to something newer like BBR=E2=80=A6 so seems like CUBIC *should* b= e performing fine on this WAN link, and the difference is something else.)<= /div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div><div dir=3D"au= to">=E2=80=94Matt</div><div dir=3D"auto"><br></div><div dir=3D"auto"><br></= div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor= der-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-col= or:rgb(204,204,204)" dir=3D"auto"></blockquote> </div> </div> --000000000000b0f07f05f38398b8--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANwXMPNBkWQHzT4f%2Bjy0RV1gK7R6nJOWYsG5NZTf9RadRDNfXg>