From: "Klatsky, Carl" <Carl_Klatsky@comcast.com>
To: jb <justin@dslr.net>, Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] 22 seconds til bloat on gfiber?
Date: Sun, 23 Oct 2016 16:14:24 +0000 [thread overview]
Message-ID: <f0e2a4156d08421dbc5b2e1e99412c34@PACDCEX43.cable.comcast.com> (raw)
In-Reply-To: <CAH3Ss96JhxytQitYuq5YWqPB+pN5JHEW7jAHKH-pA=G5KD7_oQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
Justin,
How does one initiate the ‘hi-res’ tests? On the site, I am only seeing the regular speed / bloat test get launched.
Side comment – could you please label the graph with units? I read it as X-axis is time in seconds and Y-axis as latency in milliseconds, but having the explicit label will be helpful. Thanks.
Regards,
Carl Klatsky
I've adjusted the display to list up to 10 of the last registered users and will contact some of them to see if I can get someone to run some hi-res tests, confirm with a command line ping, and offer some insight into their hardware setup..
On Sun, Oct 23, 2016 at 7:29 PM, Jonathan Morton <chromatix99@gmail.com<mailto:chromatix99@gmail.com>> wrote:
Surely it's attached via Gigabit Ethernet? The bloat could easily be in the NIC or its drivers. That has nothing to do with Google.
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 4518 bytes --]
next prev parent reply other threads:[~2016-10-23 16:14 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-22 21:56 Dave Taht
2016-10-22 23:52 ` Jonathan Morton
2016-10-23 1:33 ` jb
2016-10-23 1:45 ` Dave Taht
2016-10-23 1:47 ` Dave Taht
2016-10-23 2:27 ` jb
[not found] ` <CAJq5cE3DsV9v6ATVeq+vF_kVFjKy+8Qjwe-P01ZZbyKZB9HC6w@mail.gmail.com>
2016-10-23 8:29 ` Jonathan Morton
2016-10-23 9:23 ` jb
2016-10-23 16:14 ` Klatsky, Carl [this message]
2016-10-24 0:46 ` jb
2016-10-24 13:13 ` Klatsky, Carl
2016-10-24 16:11 ` Noah Causin
2016-10-24 20:27 ` Klatsky, Carl
2016-10-23 2:30 ` Benjamin Cronce
2016-10-25 7:10 ` Jonas Mårtensson
2016-10-23 5:50 ` Mikael Abrahamsson
2016-10-24 16:57 ` Jonas Mårtensson
2016-10-24 22:10 ` Benjamin Cronce
2016-10-25 0:09 ` jb
2016-10-25 12:01 ` Benjamin Cronce
2016-10-25 13:11 ` Klatsky, Carl
2016-10-25 21:20 ` jb
2016-10-26 0:02 ` Klatsky, Carl
2016-10-25 15:59 ` Jan Ceuleers
2016-10-26 1:05 ` Benjamin Cronce
2016-10-26 14:49 ` Jan Ceuleers
2016-10-26 15:36 ` Mikael Abrahamsson
2016-10-27 14:32 ` Jonas Mårtensson
2016-10-27 16:56 ` Dave Taht
2016-10-27 17:56 ` [Bloat] Sidebar on s-curves David Collier-Brown
2016-10-27 19:30 ` [Bloat] 22 seconds til bloat on gfiber? David Lang
2016-10-27 19:41 ` Dave Taht
2016-10-27 19:48 ` Aaron Wood
2016-10-28 15:51 ` Jan Ceuleers
2016-10-28 15:55 ` Klatsky, Carl
2016-10-27 19:45 ` Aaron Wood
2016-10-27 20:17 ` Mikael Abrahamsson
2016-12-07 5:40 ` Jonathan Morton
2016-12-07 7:05 ` Mikael Abrahamsson
[not found] <mailman.313.1477591111.3555.bloat@lists.bufferbloat.net>
2016-10-27 19:27 ` Jonathan Foulkes
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=f0e2a4156d08421dbc5b2e1e99412c34@PACDCEX43.cable.comcast.com \
--to=carl_klatsky@comcast.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=justin@dslr.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