From: Maciej Soltysiak <maciej@soltysiak.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] collecting some data?
Date: Mon, 25 Feb 2013 21:40:53 +0100 [thread overview]
Message-ID: <CAMZR1YBgMtFnkbJi6t7VObdKarLX+aeGHh7SuHDTwV8rXwChCg@mail.gmail.com> (raw)
In-Reply-To: <CAMZR1YBLr2uDURGfxS+DVxRRuFYr0XHj2eJ8-FD9-fdU48AwKg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]
On Mon, Feb 25, 2013 at 9:39 PM, Maciej Soltysiak <maciej@soltysiak.com>wrote:
> On Mon, Feb 25, 2013 at 9:13 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
>> I have been collecting statistics on the behavior of the 3.7.5-2 version
>> of cerowrt, and perhaps y'all out there can help. I've been doing four
>> repeatable tests.
>>
>> I feed the attached file into the chrome web page benchmark and run it 4
>> times:
>>
>> 1) No other load on the system
>> 2) while running a single up and single down netperf stream to icei.org(on the east coast)
>> 3) then while still loaded, after turning on simple_qos.sh, set for ~85%
>> of the rated up/down bandwidth...
>> 4) then killing the load, and keeping simple_qos enabled.
>>
> Is that good if I run the chrome benchmark from a win7 laptop on 802.11n
> wifi, while netperfs are going from the wndr3800?
>
Forgot to mention my win7 TCP setup is:
netsh interface>tcp show global
Querying active state...
TCP Global Parameters
----------------------------------------------
Receive-Side Scaling State : enabled
Chimney Offload State : automatic
NetDMA State : enabled
Direct Cache Acess (DCA) : disabled
Receive Window Auto-Tuning Level : normal
Add-On Congestion Control Provider : none
ECN Capability : enabled
RFC 1323 Timestamps : disabled
Regards,
Maciej
[-- Attachment #2: Type: text/html, Size: 2296 bytes --]
next prev parent reply other threads:[~2013-02-25 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 20:13 Dave Taht
2013-02-25 20:22 ` Dave Taht
2013-02-25 20:39 ` Maciej Soltysiak
2013-02-25 20:40 ` Maciej Soltysiak [this message]
2013-02-25 20:44 ` Dave Taht
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=CAMZR1YBgMtFnkbJi6t7VObdKarLX+aeGHh7SuHDTwV8rXwChCg@mail.gmail.com \
--to=maciej@soltysiak.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@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