On Mon, Feb 25, 2013 at 3: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?

sure. 

So long as the circumstances are documented, all data is good. (well, a start!) I note it would be helpful to also collect the ping rtt to the netperf server you are using....
 

Regards,
Maciej



--
Dave Täht

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