From: Hal Murray <hmurray@megapathdsl.net>
To: bloat@lists.bufferbloat.net
Cc: Hal Murray <hmurray@megapathdsl.net>
Subject: [Bloat] Measuring Latency
Date: Sat, 13 Sep 2014 12:41:26 -0700 [thread overview]
Message-ID: <20140913194126.5B0D1406062@ip-64-139-1-69.sjc.megapath.net> (raw)
> When reading it, it strikes me, that you don't directly tell them what to
> do; e.g. add a latency test during upload and download. ...
Does round trip latency have enough info, or do you need to know how much is
contributed by each direction?
If I gave you a large collection of latency data from a test run, how do you
reduce it to something simple that a marketer could compare with the results
from another test run?
--
These are my opinions. I hate spam.
next reply other threads:[~2014-09-13 19:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-13 19:41 Hal Murray [this message]
2014-09-13 19:48 ` Sebastian Moeller
2014-09-13 23:32 ` Jonathan Morton
2014-09-14 14:31 ` Neil Davies
2014-09-14 16:55 ` Sebastian Moeller
2014-09-14 17:26 ` Neil Davies
2014-09-14 16:57 ` Jonathan Morton
[not found] ` <1410691150.20919.YahooMailNeo@web122503.mail.ne1.yahoo.com>
2014-09-14 17:51 ` [Bloat] Fw: " Alex Burr
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=20140913194126.5B0D1406062@ip-64-139-1-69.sjc.megapath.net \
--to=hmurray@megapathdsl.net \
--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