[Cerowrt-devel] speedtest.sh script available

[Dave Taht]

running a test to snapon (15ms away) gives me much better results for
a single tcp flow and downloads
set to 30000

(rich: is ecn enabled on your server?)

root at comcast-gw:~# ./speedtest.sh -H snapon.lab.bufferbloat.net
Testing against snapon.lab.bufferbloat.net while pinging gstatic.com
(60 seconds in each direction)
............................................................
 Download:  27.63 Mbps
  Latency: (in msec, 61 pings, 0.00% packet loss)
      Min: 16.205
    10pct: 18.351
   Median: 20.750
      Avg: 21.596
    90pct: 24.881
      Max: 33.364
............................................................
   Upload:  4.13 Mbps
  Latency: (in msec, 61 pings, 0.00% packet loss)
      Min: 16.092
    10pct: 20.611
   Median: 24.177
      Avg: 23.993
    90pct: 26.961
      Max: 31.142



On Tue, Mar 25, 2014 at 10:13 AM, Dave Taht <dave.taht at gmail.com> wrote:
> aaron: tcp is highly sensitive to RTT and I imagine the rtt from paris
> to his server is rather high. See
> what happens via demo.tohojo.dk which is much closer to you.
>
> (ping times between there and rich's server would be good to have)
>
>
>
> On Tue, Mar 25, 2014 at 9:09 AM, Aaron Wood <woody77 at gmail.com> wrote:
>> 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 at 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 at lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>
>>
>>
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel at lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>
>
>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html