From: Sebastian Moeller <moeller0@gmx.de>
To: Ernesto Elias <ernestogelias@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Routing limit question
Date: Sun, 19 Oct 2014 21:55:53 +0200 [thread overview]
Message-ID: <B1284EB6-8C34-42A9-831F-72B5B2D96D2C@gmx.de> (raw)
In-Reply-To: <CAAMzHDZECTJ7xHzebyRke17XP=3ce6aNadiDKn=d9bRx+QfDOg@mail.gmail.com>
Hi Ernesto,
I would recommend to not run the netperf processes on the router you want to assess, if possible. Shaping at the rates you are interested in probably will take 100% CPU of the router, so there is no slack for running net server and netperf instances at the same time. Also I would recommend to use netperf-wrapper (https://github.com/tohojo/netperf-wrapper) instead of netperfrunner.sh as it allows so much nicer visualization of the queueing over time. netperfrunner.sh is great tool for quick testing and figuring out link capacities and worst case latency under load increase (LULI), but for more thorough comparisons it ain’t made. Netperf-wrapper will run under linux and macosx natively, but will also run (well enough) in a linux virtual machine on a windows box.
Best Regards
Sebastian
On Oct 19, 2014, at 21:16 , Ernesto Elias <ernestogelias@gmail.com> wrote:
> root@cerowrt:~# /usr/lib/CeroWrtScripts/netperfrunner.sh
> 2014-10-19 15:10:27 Testing netperf.bufferbloat.net (ipv4) with 4 streams down a nd up while pinging gstatic.com. Takes about 60 seconds.
> Download: 30.49 Mbps
> Upload: 46.52 Mbps
> Latency: (in msec, 61 pings, 0.00% packet loss)
> Min: 19.848
> 10pct: 19.958
> Median: 20.743
> Avg: 21.229
> 90pct: 22.739
> Max: 30.491
> root@cerowrt:~# /usr/lib/CeroWrtScripts/netperfrunner.sh
> 2014-10-19 15:11:54 Testing netperf.bufferbloat.net (ipv4) with 4 streams down a nd up while pinging gstatic.com. Takes about 60 seconds.
> Download: 7.02 Mbps
> Upload: 63.68 Mbps
> Latency: (in msec, 61 pings, 0.00% packet loss)
> Min: 21.690
> 10pct: 117.997
> Median: 153.983
> Avg: 150.851
> 90pct: 180.777
> Max: 190.265
>
>
> The first result i gotten by only shaping the uplink and the second results are for only shaping the downlink...
>
> and for the testing i put 0 on the for the downlink and uplink when I was testing for the opposite. and I put 50000 in it when I was shaping it for the test. Am I doing it right ?
>
> On Sun, Oct 19, 2014 at 2:51 PM, Dave Taht <dave.taht@gmail.com> wrote:
> shape the download only, then measure. shape the upload only, then measure.
>
> On Sun, Oct 19, 2014 at 11:48 AM, Ernesto Elias <ernestogelias@gmail.com> wrote:
> > Oh OK I mean I was just wondering because I was trying to figure out what
> > should I have put in the sqm tab because I saw that the wndr3800 tops out at
> > 50 mbit combined of download and upload right? As of now I have it at 25/25
> > on the page. Is that right or should I just shape the upload?
> >
> > On Oct 19, 2014 2:24 PM, "Dave Taht" <dave.taht@gmail.com> wrote:
> >>
> >> On at least one verizon device I've tried it appeared that they had
> >> SFQ or something similar on egress from the modem.
> >>
> >>
> >> http://www.bufferbloat.net/projects/codel/wiki/RRUL_Rogues_Gallery#Verizon-FIOS-Testing-at-25Mbit-up-and-25Mbit-down
> >>
> >> So you only needed to shape the download. which is good as we start
> >> peaking out at 50Mbit download total. But only measurements can tell.
> >>
> >>
> >> On Sun, Oct 19, 2014 at 10:51 AM, Ernesto Elias <ernestogelias@gmail.com>
> >> wrote:
> >> > Hello everyone!
> >> > I have a question about the wndr3800 routing limit. I went back to the
> >> > older
> >> > submissions to see if I can find what would be the answer for it. But in
> >> > my
> >> > search I haven't managed to find a definite answer. From what I seen
> >> > about
> >> > setting the limit it can do with SQM is 50, 60, or 80 mbit. I'm just
> >> > wondering if anyone can shed some light for me here as I have verizon
> >> > fios
> >> > and my speeds are 50 dl/50 ul. Thank you guys very much!
> >> >
> >> > _______________________________________________
> >> > Cerowrt-devel mailing list
> >> > Cerowrt-devel@lists.bufferbloat.net
> >> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
> >> >
> >>
> >>
> >>
> >> --
> >> Dave Täht
> >>
> >> thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
>
>
>
> --
> Dave Täht
>
> thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2014-10-19 19:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 17:51 Ernesto Elias
2014-10-19 18:24 ` Dave Taht
2014-10-19 18:48 ` Ernesto Elias
2014-10-19 18:51 ` Dave Taht
2014-10-19 19:16 ` Ernesto Elias
2014-10-19 19:55 ` Sebastian Moeller [this message]
2014-10-20 1:08 ` Ernesto Elias
2014-10-20 8:11 ` Sebastian Moeller
2014-10-21 2:30 ` Ernesto Elias
2014-10-21 8:23 ` Sebastian Moeller
2014-10-22 19:39 ` Ernesto Elias
2014-10-22 20:36 ` Sebastian Moeller
2014-10-23 22:03 ` Ernesto Elias
2014-10-24 11:38 ` Sebastian Moeller
2014-10-19 18:56 ` Sebastian Moeller
2014-10-19 19:22 ` Dave Taht
2014-10-19 19:33 ` Ernesto Elias
2014-10-19 19:41 ` Dave Taht
[not found] ` <CAA93jw6DFxoDaRVCoQn=zxbOjgQ-dA1bCZ1W=p9br25jWrRgkg@mail.gmail.com>
2014-10-19 22:44 ` Sebastian Moeller
2014-10-20 20:04 ` Dave Taht
2014-10-20 22:48 ` Dave Taht
2014-10-21 3:35 ` Aaron Wood
2014-10-21 7:43 ` Sebastian Moeller
2014-10-21 7:51 ` Sebastian Moeller
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=B1284EB6-8C34-42A9-831F-72B5B2D96D2C@gmx.de \
--to=moeller0@gmx.de \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=ernestogelias@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