From: jb <justin@dslr.net>
To: Jesper Dangaard Brouer <brouer@redhat.com>,
bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] New speedtest with bufferbloat indicators (from DSLreports)
Date: Tue, 28 Apr 2015 18:14:27 +1000 [thread overview]
Message-ID: <CAH3Ss94eLpXZpomEqNscPQByUqUoV-jCRVn-GZTGkC+UbnQWOQ@mail.gmail.com> (raw)
In-Reply-To: <CAH3Ss97FpcpJWdX6zLhSKt3s9LepnZFT=j9UWvqQTgYT6onHXw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2455 bytes --]
Oh, and if you are trying to reach the local speedtest.net speed, but
select 4g, it is defaulting to 3 streams, and then only 1 up because of the
old Firefox version,
and is using servers in Netherlands and Germany.
So if you try a current version of Firefox and/or Chrome, and want to push
it,
change in preferences streams down to 6 and streams up to 2 - 4
On Tue, Apr 28, 2015 at 5:57 PM, jb <justin@dslr.net> wrote:
> Regarding
> http://www.dslreports.com/speedtest/380810
>
> The upload graph was broken, or partially so, because you're using
> Firefox/24.0 which dates from 2014 and apparently doesn't know how to
> feedback information on the upload so the measurement was done from each
> upload as it finished
>
> So that is why the upload graph is no good, but the upload number is about
> right.
>
> Also it did have stalls and drops but not too bad, not enough to trigger
> an error.
> 46.98s 10hz drop stats frames=15 total ms=3985
>
>
> On Tue, Apr 28, 2015 at 5:22 PM, Jesper Dangaard Brouer <brouer@redhat.com
> > wrote:
>
>>
>> On Tue, 28 Apr 2015 10:03:48 +0300 Marko Myllynen <myllynen@redhat.com>
>> wrote:
>>
>> > On 2015-04-28 09:55, Jesper Dangaard Brouer wrote:
>> > >
>> > > Finally, there is a easy-to-use browser based speedtest that also
>> > > measures bufferbloat:
>> > >
>> > > http://www.dslreports.com/speedtest
>> > >
>> > > After you run the test, click the green "Results + Share" button to
>> see
>> > > more detailed information. Which will contain a graph with "Ping
>> > > response under load", which will indicate if you have bufferbloat on
>> > > your link.
>> >
>> > FWIW, my results using RHEL 6 + Lenovo T420s + 4G modem:
>>
>> Thanks - I'm surprised to see how well 4G handles this. I was
>> expecting to see higher delays under load.
>>
>> > http://www.dslreports.com/speedtest/380810
>>
>> The upload graph looks a little strange.
>>
>> > http://www.speedtest.net/my-result/4322094820
>> >
>> > Speedtest has servers in Finland so that might explain a bit. I was
>> > running two Fedora guest installations in the background during the
>> > tests so the system was rather busy.
>>
>> Could you try to run this in a Chrome browser?
>> The author (Cc'ed) sayed Firefox on Linux is too slow...
>>
>> --
>> Best regards,
>> Jesper Dangaard Brouer
>> MSc.CS, Sr. Network Kernel Developer at Red Hat
>> Author of http://www.iptv-analyzer.org
>> LinkedIn: http://www.linkedin.com/in/brouer
>>
>
>
[-- Attachment #2: Type: text/html, Size: 4001 bytes --]
prev parent reply other threads:[~2015-04-28 8:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150428085509.168471ca@redhat.com>
[not found] ` <553F30D4.60103@redhat.com>
[not found] ` <20150428092235.32205a07@redhat.com>
2015-04-28 7:57 ` jb
2015-04-28 8:14 ` jb [this message]
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=CAH3Ss94eLpXZpomEqNscPQByUqUoV-jCRVn-GZTGkC+UbnQWOQ@mail.gmail.com \
--to=justin@dslr.net \
--cc=bloat@lists.bufferbloat.net \
--cc=brouer@redhat.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