From: Stefan Alfredsson <stefan.alfredsson@kau.se>
To: <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] different speeds on different ports? (benchmarking fun)
Date: Thu, 21 Sep 2017 12:58:39 +0200 [thread overview]
Message-ID: <d2689f0b-e016-7013-ecca-df0f92101048@kau.se> (raw)
In-Reply-To: <CALQXh-O+Nq3g6mNiDs-J1bA=VL3yynB0NQTyqHEUgnenPKc3iA@mail.gmail.com>
On 2017-08-30 07:15, Aaron Wood wrote:
>
> The current hypothesis that we have is that this is due to either
> traffic class, or the ports that traffic are running on. I've ruled
> out the ping streams, as a parallel set of netperf tcp_maerts
> downloads has the same 120Mbps roof.
Also think of server differentiation (maybe full capacity to known
measurement servers, shaped for other destinations). Does dslreports
have flent/netperf responders on their servers as well?
>
> It would be interesting if we could run some netperf tests using port
> 80/443 for the listening socket for the data connection (although if
> doing deep-packet inspection, we might need to use an actual HTTP
> transfer).
UDP 443 (QUIC) would also be interesting for comparison.
/Stefan
next prev parent reply other threads:[~2017-09-21 10:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-30 5:15 Aaron Wood
2017-09-21 2:06 ` Dave Taht
2017-09-21 2:34 ` Dave Taht
2017-09-21 10:58 ` Stefan Alfredsson [this message]
2017-09-21 11:16 ` Toke Høiland-Jørgensen
2017-09-21 12:51 ` Sebastian Moeller
2017-09-22 0:26 ` David Lang
2017-09-21 14:50 ` Colin Dearborn
2017-09-21 15:13 ` Aaron Wood
2017-09-21 15:16 ` Aaron Wood
2017-09-23 2:51 ` Aaron Wood
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=d2689f0b-e016-7013-ecca-df0f92101048@kau.se \
--to=stefan.alfredsson@kau.se \
--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