From: jb <justin@dslr.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] the dslreports png
Date: Wed, 29 Apr 2015 01:22:17 +1000 [thread overview]
Message-ID: <CAH3Ss94V1eA4io4H1aYb0RUmOmzHwuwg9aT_TeBg+dAyNuF5Gw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5TUQJX47_52zjoR3Y9ZM9SnMuazECzq0aWXMphScbP-w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]
I agree! but I don't want to rush. What latency should substitute? average?
median? latency during upload? download? both? should it be the excess over
idle ping, expressed as a multiplier? an absolute value?
Most people as in 98% of people who use this test do so without any
reference to instructions the forums or anything else and all of them
"expect" to see latency
pings that are similar to speedtest.net measure of how close the speed test
server is.
And I haven't even sorted out the latency bugs. I just now asked the nginx
development list why IE11 has problems doing http pings because it does
a weird two-step of high-normal-high-normal, but when talking to nginx only!
it behaves ok when talking to google.com.
There is a jsfiddle you can play with to see the problem (I hope!)
http://jsfiddle.net/qe44nbwh/
change nginx.org to google.com, using IE11. (other browsers work fine)
On Wed, Apr 29, 2015 at 12:23 AM, Dave Taht <dave.taht@gmail.com> wrote:
> http://dfkrkqaqb1zsx.cloudfront.net/speedtest/cdn/377727.png
>
> is showing the base latency without load. It would be more effective
> if it showed the
> latency with load.
>
> --
> Dave Täht
> Open Networking needs **Open Source Hardware**
>
> https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67
>
[-- Attachment #2: Type: text/html, Size: 2232 bytes --]
next prev parent reply other threads:[~2015-04-28 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 14:23 Dave Taht
2015-04-28 15:22 ` jb [this message]
2015-04-28 20:21 ` Toke Høiland-Jørgensen
2015-04-28 20:24 ` David Lang
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=CAH3Ss94V1eA4io4H1aYb0RUmOmzHwuwg9aT_TeBg+dAyNuF5Gw@mail.gmail.com \
--to=justin@dslr.net \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@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