From: Dave Taht <dave.taht@gmail.com>
To: Aaron Wood <woody77@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] different speeds on different ports? (benchmarking fun)
Date: Wed, 20 Sep 2017 19:06:35 -0700 [thread overview]
Message-ID: <CAA93jw7k1XDrJYbH5aYxqZ5SdYm4YenMC5A4zGC6hhujTvBYWQ@mail.gmail.com> (raw)
In-Reply-To: <CALQXh-O+Nq3g6mNiDs-J1bA=VL3yynB0NQTyqHEUgnenPKc3iA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 214 bytes --]
Well, at these higher speeds the distance to the server and the quality of
the server and its cloud connection start to matter. I'm assuming you are
using flent-fremont which should only be 10-12 ms away from you?
[-- Attachment #2: Type: text/html, Size: 243 bytes --]
next prev parent reply other threads:[~2017-09-21 2:06 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 [this message]
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=CAA93jw7k1XDrJYbH5aYxqZ5SdYm4YenMC5A4zGC6hhujTvBYWQ@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=woody77@gmail.com \
/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