From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] gitlab network optimizations
Date: Thu, 7 Apr 2022 09:53:13 -0700 [thread overview]
Message-ID: <CAA93jw6xhdhrNzFibb4Z-19Ls1msEGDsXdjcS8_Dcp1RNLqRVw@mail.gmail.com> (raw)
Most cloud operations websites are kept internal. gitlab's is not,
which is pretty cool. In looking over this:
https://gitlab.com/gitlab-com/gl-infra/production/-/issues/6768
They are tracking tcp syn retransmits, but not drops or other
congestion control related info. And
also
sysctl net.ipv4.tcp_notsent_lowat=4294967295;
where we've been getting good results with that set as low as 32k.
Anyone know anyone at gitlab?
--
I tried to build a better future, a few times:
https://wayforward.archive.org/?site=https%3A%2F%2Fwww.icei.org
Dave Täht CEO, TekLibre, LLC
reply other threads:[~2022-04-07 16:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw6xhdhrNzFibb4Z-19Ls1msEGDsXdjcS8_Dcp1RNLqRVw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox