From: Simon Barber <simon@superduper.net>
To: jb <justin@dslr.net>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] delay-under-load really helps diagnose real world problems
Date: Fri, 24 Apr 2015 21:42:44 -0700 [thread overview]
Message-ID: <14ceee27200.27f7.e972a4f4d859b00521b2b659602cb2f9@superduper.net> (raw)
In-Reply-To: <CAH3Ss958YFw5YzoB2zGUmCHCKA8ZD0=45UuXF4hfj7wXAgEzng@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2483 bytes --]
This is a great tool. Just ran another test from my cell, this time not
selecting the 'desktop' mode, and choosing 4G as my access method.
Similar results to the last one.
http://www.dslreports.com/speedtest/359928
Perhaps on the mobile platforms you could include a button on the results
page to show the latency graph, but not actually load it until the button
is pressed.
Simon
Sent with AquaMail for Android
http://www.aqua-mail.com
On April 24, 2015 9:13:12 PM jb <justin@dslr.net> wrote:
> Apologies, it is sorted. Try now on mobile. There is a new box coloured
> purple!
>
> Multiple issues, main one being the Highcharts charting js plugin is quite
> heavy at 200kb, so I am opting to not use it for the results page on mobile
> at least not yet. Perhaps if one is on 4G I should not worry,.
>
> However now, either way, the response is displayed during the test (in the
> purple box) and also stored.
> So viewing past tests in desktop mode still shows everything.
>
>
> On Sat, Apr 25, 2015 at 12:56 PM, Simon Barber <simon@superduper.net> wrote:
>
> > I ran some tests from my cellphone - a Samsung Note 3. I had to select
> > 'request desktop site' as an option in the chrome browser, and not choose
> > '4G' as my connection type (I chose DSL), to get the latency measurement to
> > show up. The results are great though.
> >
> > http://www.dslreports.com/speedtest/355893
> >
> > Download bloat (buffer in the cell site) is bad, but not absolutely
> > horrible, at about 1.1 seconds. Upload direction is terrible - 5.8 seconds
> > by the end of the test, and would probably have been higher given a longer
> > test. I'm assuming that this buffer is in the modem in the handset, and is
> > likely an almost infinite buffer.
> >
> > Simon
> >
> >
> > On 4/24/2015 7:58 AM, Matthew Ford wrote:
> >
> >> On 23 Apr 2015, at 22:55, Bill Ver Steeg (versteb) <versteb@cisco.com>
> >>> wrote:
> >>>
> >>> So, hats off to Justin!
> >>>
> >> A big +1 to what Bill said from me. This tool is great and has already
> >> helped me improve my own home network setup.
> >>
> >> A colleague noted that selecting ‘Public WiFi’ as connection type results
> >> in no bloat measurements. Which connection types are bloat measurements
> >> enabled for? What’s the plan for the others?
> >>
> >> Mat
> >> _______________________________________________
> >> Bloat mailing list
> >> Bloat@lists.bufferbloat.net
> >> https://lists.bufferbloat.net/listinfo/bloat
> >>
> >
> >
[-- Attachment #2: Type: text/html, Size: 4119 bytes --]
prev parent reply other threads:[~2015-04-25 4:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 21:55 Bill Ver Steeg (versteb)
2015-04-24 14:58 ` Matthew Ford
2015-04-25 2:23 ` jb
2015-04-25 2:56 ` Simon Barber
2015-04-25 4:13 ` jb
2015-04-25 4:42 ` Simon Barber [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=14ceee27200.27f7.e972a4f4d859b00521b2b659602cb2f9@superduper.net \
--to=simon@superduper.net \
--cc=bloat@lists.bufferbloat.net \
--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