From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] 3.10.36-1 dev build released
Date: Sat, 5 Apr 2014 17:51:43 -0700 [thread overview]
Message-ID: <CAA93jw5ieGfux=Fi9Q2t_Xtm6HCYXWCojX5bKf+q4SvrSwsgkQ@mail.gmail.com> (raw)
In-Reply-To: <20140406000236.GM9694@angus.ind.WPI.EDU>
On Sat, Apr 5, 2014 at 5:02 PM, Chuck Anderson <cra@wpi.edu> wrote:
> Here are some betterspeedtest.sh results for 3.10.36-1:
>
> First, without SQM enabled:
>
> root@cerowrt:~# sh betterspeedtest.sh
> Testing against netperf.richb-hanover.com while pinging gstatic.com (60 seconds in each direction)
> ............................................................
> Download: 52.39 Mbps
> Latency: (in msec, 61 pings, 0.00% packet loss)
> Min: 15.281
> 10pct: 18.302
> Median: 28.502
> Avg: 32.891
> 90pct: 56.776
> Max: 74.282
> .............................................................
> Upload: 11.07 Mbps
> Latency: (in msec, 61 pings, 0.00% packet loss)
> Min: 15.341
> 10pct: 18.669
> Median: 82.480
> Avg: 126.662
> 90pct: 248.102
> Max: 278.644
>
> And now, with SQM set to 80% up/down numbers from above:
>
> root@cerowrt:~# sh betterspeedtest.sh
> Testing against netperf.richb-hanover.com while pinging gstatic.com (60 seconds in each direction)
> ............................................................
> Download: 32.84 Mbps
> Latency: (in msec, 61 pings, 0.00% packet loss)
> Min: 15.623
> 10pct: 16.077
> Median: 17.634
> Avg: 17.982
> 90pct: 19.653
> Max: 23.272
> .............................................................
> Upload: 8.25 Mbps
> Latency: (in msec, 61 pings, 0.00% packet loss)
> Min: 16.001
> 10pct: 17.623
> Median: 19.796
> Avg: 19.820
> 90pct: 21.716
> Max: 23.228
> root@cerowrt:~#
I think we are establishing that you can set downloads to above the
measured value at above 22mbit. Please try again with download 60000,
and pick another number for uploads higher than 80%.
>
>
> On Sat, Apr 05, 2014 at 01:18:51PM -0700, Dave Taht wrote:
>> + openwrt merge
>> ++ fix for dhcpv6 renew problem
>> + actually tested for an hour so far on 5.4ghz, with a us countrycode
>> and wpa+psk enabled...
>>
>> Get it at:
>>
>> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.36-1/
>>
>> but: there isn't much other reason to upgrade to this...
>>
>> - no progress on the wifi bug - but I am beating up wifi with a variety of
>> devices and scripts today hoping to make it fail, and bringing up a
>> bunch more tomorrow.
>>
>> - toke's script relies on stratum '16' changing, and it doesn't with openwrt's
>> ntp, it seems....
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
prev parent reply other threads:[~2014-04-06 0:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-05 20:18 Dave Taht
2014-04-06 0:02 ` Chuck Anderson
2014-04-06 0:08 ` Chuck Anderson
2014-04-06 0:57 ` Dave Taht
2014-04-06 4:48 ` Chuck Anderson
2014-04-06 21:44 ` Dave Taht
2014-04-06 0:51 ` Dave Taht [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/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='CAA93jw5ieGfux=Fi9Q2t_Xtm6HCYXWCojX5bKf+q4SvrSwsgkQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.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