From: jb <justin@dslr.net>
To: Rich Brown <richb.hanover@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Differences between dslr cli program vs. web test
Date: Sun, 20 Nov 2016 12:05:12 +1100 [thread overview]
Message-ID: <CAH3Ss94a8Xr5_qYV-mofOxWZNJ=k7APJFkwN5g-0uBs75zHdfA@mail.gmail.com> (raw)
In-Reply-To: <6C19376A-CDCD-44B3-9A14-A70C136980C5@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1530 bytes --]
I'll run some tests myself however can you compare using the same number of
streams?
the CLI in this example is doing 18 down and 12 up, the web is doing - for
your connection speed - a more
reasonable 8 down and 2 up and has a correspondingly lower re-transmit
error rate on the server side.
Also can you compare just 1 stream down and 1 up?
thanks
On Fri, Nov 18, 2016 at 3:08 PM, Rich Brown <richb.hanover@gmail.com> wrote:
> I find a marked difference between the measurements that come from the
> dslr cli program and the web tester.
>
> The CLI seems to show slower speeds than the web tester. Here's data from
> one web run, and two CLI runs.
>
> I'm running on a mid-2015 MacBook Pro, 2.5 GHz i7, 16 GBytes of RAM, OSX
> 10.10.5, with 7mbps/768kbps DSL. What other information would you want to
> see? Thanks!
>
> Rich
>
> -----------
> Web GUI: http://www.dslreports.com/speedtest/6241603 (shows 6.91/0.57
> Mbps)
>
> bash-3.2$ ./dslrcli-darwin-amd64 --version
> Dslrcli version 0.1 - 15-Nov-2016
>
> bash-3.2$ ./dslrcli-darwin-amd64 --uploadtime 30 --downloadtime 30
> Selecting nearest servers....
> Download Testing.....
> Upload Testing.....
> Uploading results...
> Download : 6.62 Megabit/sec Upload : 901.93 Kilobit/sec
> http://www.dslreports.com/speedtest/6241561
>
> bash-3.2$ ./dslrcli-darwin-amd64
> Selecting nearest servers....
> Download Testing.....
> Upload Testing.....
> Uploading results...
> Download : 6.58 Megabit/sec Upload : 778.23 Kilobit/sec
> http://www.dslreports.com/speedtest/6241492
[-- Attachment #2: Type: text/html, Size: 2313 bytes --]
prev parent reply other threads:[~2016-11-20 1:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 4:08 Rich Brown
2016-11-20 1:05 ` 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='CAH3Ss94a8Xr5_qYV-mofOxWZNJ=k7APJFkwN5g-0uBs75zHdfA@mail.gmail.com' \
--to=justin@dslr.net \
--cc=bloat@lists.bufferbloat.net \
--cc=richb.hanover@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