From: Alan Jenkins <alan.christopher.jenkins@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] new public web tests for bufferbloat
Date: Thu, 2 Jun 2016 00:02:36 +0100 [thread overview]
Message-ID: <CANmMgnEB4PyRNd6XF3vNa9-Q31e2qORix+fQF3X1YucS6E7Z9g@mail.gmail.com> (raw)
In-Reply-To: <CANmMgnEeL4__b9hfk3qVvGq38wSqZP5KtLg6k13SwhO0K83D7w@mail.gmail.com>
On 01/06/2016, Alan Jenkins <alan.christopher.jenkins@gmail.com> wrote:
> On 01/06/2016, Dave Taht <dave.taht@gmail.com> wrote:
>> see: http://labs.thinkbroadband.com/speedtest/
>>
>> (can't test myself, not being in england - can someone there test it
>> and post results/screenshots?)
>
> http://www.thinkbroadband.com/speedtest/results.html?id=1464821570474383655
>
> (OpenWrt SQM. ISP _download_ is un-bloated already, for reasonable
> numbers of streams. Though even with SQM, downloading multiple
> torrents in Transmission can cause both latency up to 100ms & packet
> loss).
oops...
the results page above omits the bufferbloat result. The original
result has a sharing button that requires a Facebook login. Here's
the screenshot
https://dl.dropboxusercontent.com/u/49925445/bufferbloat.net/thinkbroadband.com/2016-06-01%20labs.thinkbroadband.com%20speedtest.png
>> and:
>>
>> https://sourceforge.net/speedtest/
>>
>> which is quite pretty, if mildly confusing.
>>
>>
>> I have issues with the language and testing methodologies, of course,
>> but it is good to see these arrive. When will speedtest.net get it
>> right?
next prev parent reply other threads:[~2016-06-01 23:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 16:55 Dave Taht
2016-06-01 22:58 ` Alan Jenkins
2016-06-01 23:02 ` Alan Jenkins [this message]
2016-06-01 23:06 ` Alan Jenkins
2016-06-02 0:58 ` Dave Taht
[not found] ` <CAA93jw7hqkDBbRY4sSJEoACGGs6kmsntHSDzqQzbZW+oRsgcrw@mail.gmail.com>
2016-06-02 15:19 ` Alan Jenkins
2016-06-02 8:31 ` moeller0
[not found] <mailman.1112.1464880746.3642.bloat@lists.bufferbloat.net>
2016-06-02 16:54 ` Rich Brown
2016-06-02 18:57 ` Juliusz Chroboczek
2016-06-02 20:05 ` Colin Dearborn
2016-06-02 22:26 ` Kathleen Nichols
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=CANmMgnEB4PyRNd6XF3vNa9-Q31e2qORix+fQF3X1YucS6E7Z9g@mail.gmail.com \
--to=alan.christopher.jenkins@gmail.com \
--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