Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: Rich Brown <richb.hanover@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] speedtest.sh script available
Date: Tue, 25 Mar 2014 17:09:43 +0100	[thread overview]
Message-ID: <CALQXh-Put6R5aFQ+JHGhKjkTndPkJYyz49K99VJomtFVqkTu8w@mail.gmail.com> (raw)
In-Reply-To: <171F2F69-A85F-440B-8126-E9813D1EEEF0@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]

Nice!  It gives me what I'd expect for my setup, although the TCP rate is
only 2/3 the line rate on DSL (upload is better at 80%).

..............................................................
 Download:  14.09 Mbps
  Latency: (in msec, 62 pings, 0.00% packet loss)
      Min: 30.157
    10pct: 30.691
   Median: 33.412
      Avg: 34.044
    90pct: 36.970
      Max: 48.250
..............................................................
   Upload:  0.87 Mbps
  Latency: (in msec, 57 pings, 8.06% packet loss)
      Min: 30.655
    10pct: 30.744
   Median: 36.658
      Avg: 36.379
    90pct: 41.414
      Max: 46.451

I'm running 21000/1100 as my rate-limiting settings in CeroWRT (3.10.32-12).

That packet loss is what kills my UDP ping streams.  It doesn't seem to
happen if I use the Free.fr box directly, and only shows when I use CeroWRT
as the bottle-neck.

-Aaron


On Tue, Mar 25, 2014 at 4:16 PM, Rich Brown <richb.hanover@gmail.com> wrote:

> I have created a 'speedtest.sh' shell script that simulates the
> http://speedtest.net, but does it one better.
>
> The default options for the script do a separate TCP_MAERTS and TCP_STREAM
> for 60 seconds while collecting ping latency. The output of the script
> shows the down/upload speed as well as a summary of the ping latency,
> including min, max, average, median, and 10th and 90th percentiles.
>
> The script makes it easier to optimize my settings because it makes the
> latency figures more concrete. (I used to eyeball the ping output, saying,
> "Hmmm. I think there were fewer outliers than before...")
>
> You can see the script on the "Quick Test for Bufferbloat" page on the
> wiki at:
>
>
> http://www.bufferbloat.net/projects/cerowrt/wiki/Quick_Test_for_Bufferbloat#Speedtestsh-shell-script
>
> Enjoy!
>
> Rich
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>

[-- Attachment #2: Type: text/html, Size: 2969 bytes --]

  reply	other threads:[~2014-03-25 16:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25 15:16 Rich Brown
2014-03-25 16:09 ` Aaron Wood [this message]
2014-03-25 17:13   ` Dave Taht
2014-03-25 17:26     ` Dave Taht
2014-03-25 18:29     ` Aaron Wood
2014-03-25 16:35 ` Dave Taht
2014-03-25 17:09   ` Dave Taht
2014-03-25 17:58   ` Sebastian Moeller
2014-03-26 15:30   ` [Cerowrt-devel] betterspeedtest.sh (was: speedtest.sh script available) Rich Brown

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALQXh-Put6R5aFQ+JHGhKjkTndPkJYyz49K99VJomtFVqkTu8w@mail.gmail.com \
    --to=woody77@gmail.com \
    --cc=cerowrt-devel@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