From: Stefano Brivio <sbrivio@redhat.com>
To: Max Chernoff <git@maxchernoff.ca>
Cc: passt-dev@passt.top, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH v3 00/10] tcp: Fix throughput issues with non-local peers
Date: Mon, 8 Dec 2025 09:25:30 +0100 [thread overview]
Message-ID: <20251208092530.2638636a@elisabeth> (raw)
In-Reply-To: <f9ae992198f8b86df7e12b9d911c330e47aafa3c.camel@maxchernoff.ca>
Hi Max,
On Mon, 08 Dec 2025 01:11:56 -0700
Max Chernoff <git@maxchernoff.ca> wrote:
> Hi Stefano,
>
> On Mon, 2025-12-08 at 08:20 +0100, Stefano Brivio wrote:
> > With this series, I'm getting the expected (wirespeed) throughput for
> > transfers between peers with varying non-local RTTs: I checked
> > different guests bridged on the same machine (~500 us) and hosts with
> > increasing distance using iperf3, as well as HTTP transfers only for
> > some hosts I have control over (500 us and 5 ms case).
> >
> > With increasing RTTs, I can finally see the throughput converging to
> > the available bandwidth reasonably fast:
>
> Thanks for the patch, but this unfortunately seems to make things worse
> in my testing (with curl/https). Using my benchmarking script from the
> earlier thread, with a 10MB file size and a 30s timeout:
Thanks for re-testing. I actually wanted to get back to you about your
sysctl values, but, in general, I don't think things can work reliably
with the values you shared for tcp_notsent_lowat.
Does this (upload now taking longer/timing out with 50 ms RTT) also
happen without "custom" values for tcp_notsent_lowat?
I tested things quite extensively in that RTT region (without custom
sysctl values) and the improvement looks rather consistent to me.
--
Stefano
next prev parent reply other threads:[~2025-12-08 8:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 7:20 Stefano Brivio
2025-12-08 7:20 ` [PATCH v3 01/10] tcp, util: Add function for scaling to linearly interpolated factor, use it Stefano Brivio
2025-12-09 5:05 ` David Gibson
2025-12-08 7:20 ` [PATCH v3 02/10] tcp: Change usage factor of sending buffer in tcp_get_sndbuf() to 75% Stefano Brivio
2025-12-09 5:05 ` David Gibson
2025-12-08 7:20 ` [PATCH v3 03/10] tcp: Limit advertised window to available, not total sending buffer size Stefano Brivio
2025-12-08 7:20 ` [PATCH v3 04/10] tcp: Adaptive interval based on RTT for socket-side acknowledgement checks Stefano Brivio
2025-12-09 5:10 ` David Gibson
2025-12-09 22:49 ` Stefano Brivio
2025-12-08 7:20 ` [PATCH v3 05/10] tcp: Don't clear ACK_TO_TAP_DUE if we're advertising a zero-sized window Stefano Brivio
2025-12-08 7:20 ` [PATCH v3 06/10] tcp: Acknowledge everything if it looks like bulk traffic, not interactive Stefano Brivio
2025-12-09 5:12 ` David Gibson
2025-12-08 7:20 ` [PATCH v3 07/10] tcp: Don't limit window to less-than-MSS values, use zero instead Stefano Brivio
2025-12-08 7:20 ` [PATCH v3 08/10] tcp: Allow exceeding the available sending buffer size in window advertisements Stefano Brivio
2025-12-08 8:14 ` Max Chernoff
2025-12-08 8:15 ` Max Chernoff
2025-12-08 8:27 ` Stefano Brivio
2025-12-08 7:20 ` [PATCH v3 09/10] tcp: Send a duplicate ACK also on complete sendmsg() failure Stefano Brivio
2025-12-08 7:20 ` [PATCH v3 10/10] tcp: Skip redundant ACK on partial " Stefano Brivio
2025-12-08 8:11 ` [PATCH v3 00/10] tcp: Fix throughput issues with non-local peers Max Chernoff
2025-12-08 8:25 ` Stefano Brivio [this message]
2025-12-08 8:51 ` Max Chernoff
2025-12-08 9:00 ` Stefano Brivio
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251208092530.2638636a@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=git@maxchernoff.ca \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).