General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] different speeds on different ports? (benchmarking fun)
Date: Wed, 30 Aug 2017 05:15:42 -0000	[thread overview]
Message-ID: <CALQXh-O+Nq3g6mNiDs-J1bA=VL3yynB0NQTyqHEUgnenPKc3iA@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1302 bytes --]

I don't have a full writeup yet, but wanted to ask if people on here have
run into this.

I'm seeing a disparity between flent and the dslreports speed tests.  On my
connection at home (Comcast 150/12), I figured it was something related to
the test implementations, but minor.  But on a connect at a friend with
business-class Comcast (300/12), we're seeing a huge difference.  Flent
can't seem to achieve more than 120Mbps, often with an early, couple-second
hump at a much higher speed.  But dslreports' speed tests gets the full
300Mbps.

In looking closer at my connection, with sqm (cake) turned off, I'm seeing
~180Mbps download with 500ms of bufferbloat when I use the dslreports test (
http://www.dslreports.com/speedtest/20805152).

Yet flent can't come close to that, even with the tcp_12down test:

​
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.

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).

-Aaron

[-- Attachment #1.2: Type: text/html, Size: 1611 bytes --]

[-- Attachment #2: raw.totals.png --]
[-- Type: image/png, Size: 257944 bytes --]

             reply	other threads:[~2017-08-30  5:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-30  5:15 Aaron Wood [this message]
2017-09-21  2:06 ` Dave Taht
2017-09-21  2:34 ` Dave Taht
2017-09-21 10:58 ` Stefan Alfredsson
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='CALQXh-O+Nq3g6mNiDs-J1bA=VL3yynB0NQTyqHEUgnenPKc3iA@mail.gmail.com' \
    --to=woody77@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