Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Pete Heist <peteheist@gmail.com>
To: Dave Taht <dave@taht.net>
Cc: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] cake flenter results round 2
Date: Tue, 28 Nov 2017 21:35:06 +0100	[thread overview]
Message-ID: <6F2894AD-87EA-4EFC-918E-625E49EDA977@gmail.com> (raw)
In-Reply-To: <87zi76xlw5.fsf@nemesis.taht.net>


> On Nov 28, 2017, at 8:07 PM, Dave Taht <dave@taht.net> wrote:
> 
> Pete Heist <peteheist@gmail.com> writes:
> 
>> *** Round 3 Plans:
>> 
>> * Use netem to test a spread of simulated rtts and bandwidths.
> 
> Since you are leveraging a few too few boxes, attached are my current
> scripts for fiddling a bit with network namespaces. I added individual
> ssh, irtt, etc, servers so that things like flent's ssh stuff should
> just work for polling stats.

You mean a few too few virtual boxes, not necessarily physical ones, right? :) In other words, there are different topologies that can be used for testing. In your scripts you’re simulating "Internet access", where client is the family or organization for example and server is stuff on the Internet:

client - middlebox - delay - server

In my earlier point-to-point WiFi testing I was simulating an ISP’s backhaul:

client - client_router - station ----- ap - server_router - server

In my current testing I’m simulating, well, something far less useful if I think about it- two boxes blasting traffic to one another over a cable and trying to improve queueing delays between them:

client - client_router --- server_router - server

I hadn’t realized how heavy-weight traffic generation for anything beyond 4/4 flows would be at Gbit rates, or how confusing and trivial some of these results would be.

So beyond just my vague idea to “simulate a spread of rtts and bandwidths”, I see I need a topology change to produce something more useful. I think there are still two options:

1) Point-to-point WiFi again, where I’d be using two NSM5s and testing over short range at rates of up to 100 Mbps. I would probably try to get FreeNet’s APU version 1 boxes into action again so I’d have physical devices for each of the six roles above. I wish I didn’t have to use those RTL8111Es, but that’s how it is.

2) Your “Internet access” setup. Either I can get the veth stuff into action on a single physical APU2 (powerful enough?), or I can try to set up four physical boxes with the same topology (or if I were tricky, try to spread the four roles across two boxes).

#1 would be useful for FreeNet. Would it also be useful for Cake testing in general, or would you prefer more #2 results at this stage (i.e. simulating dsl, cable, satellite, etc)?


  reply	other threads:[~2017-11-28 20:35 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28 14:11 Pete Heist
2017-11-28 15:56 ` Pete Heist
2017-11-28 19:07 ` Dave Taht
2017-11-28 20:35   ` Pete Heist [this message]
2017-11-28 22:34     ` Dave Taht
2017-11-28 22:52       ` Dave Taht
2017-11-29  0:16         ` Pete Heist
     [not found]           ` <CACvFP_iY+KSUgyqrJsmpEjY8Bj5E+vCTwRhojQzUhkE2_7XVXA@mail.gmail.com>
2017-11-29  0:20             ` [Cake] Fwd: " Georgios Amanakis
2017-11-29  3:29               ` [Cake] " Georgios Amanakis
2017-11-29  4:01                 ` Dave Taht
2017-11-29 14:34                   ` Georgios Amanakis
2017-11-29 14:43                     ` Georgios Amanakis
2017-11-29 14:50                       ` Toke Høiland-Jørgensen
2017-11-29 15:33                         ` Pete Heist
2017-11-29 15:44                           ` Toke Høiland-Jørgensen
2017-11-29 16:06                             ` Georgios Amanakis
2017-11-29 17:44                               ` Dave Taht
2017-11-29 17:49                                 ` Georgios Amanakis
     [not found]                                   ` <CACvFP_hJJNJh98Eu30zEYQO5jW6CwQcxK-FBYMuOi796FwkOww@mail.gmail.com>
2017-11-29 17:51                                     ` [Cake] Fwd: " Georgios Amanakis
2017-11-29 18:00                                       ` Dave Taht
2017-11-29 18:19                                         ` Georgios Amanakis
2017-11-29 18:51                                           ` Dave Taht
2017-11-29 18:54                                             ` Georgios Amanakis
2017-11-29 20:06                                           ` Dave Taht
     [not found]                                             ` <CACvFP_iG1tTJLbpsd7YCQRH=TKX5rz4GZ8m1x34xGahSTWTgzA@mail.gmail.com>
2017-11-29 20:38                                               ` [Cake] Fwd: " Georgios Amanakis
2017-11-29 21:04                                                 ` [Cake] " Georgios Amanakis
2017-11-30 17:54                                                   ` Dave Taht
2017-11-29 17:54                                 ` [Cake] " Dave Taht
     [not found]                                   ` <CACvFP_jkqS4b1w7sfNDthx4G4_fp21P-DDFtREGMzz+zLzcThQ@mail.gmail.com>
2017-11-29 17:59                                     ` [Cake] Fwd: " Georgios Amanakis
2017-11-29 16:08                             ` [Cake] " Pete Heist
2017-11-29 16:12                               ` Georgios Amanakis
2017-11-29 16:17                                 ` Toke Høiland-Jørgensen
2017-11-29 16:21                               ` Toke Høiland-Jørgensen
2017-11-29 16:24                                 ` Georgios Amanakis
2017-11-29 16:27                                   ` Pete Heist
2017-11-29 16:36                                     ` Georgios Amanakis
2017-11-29 16:40                                       ` Toke Høiland-Jørgensen
     [not found]                                         ` <CACvFP_g66TUdpVtFuJOi_5E1XVCf1Fo1QuRf5zG4nGDExWE2JA@mail.gmail.com>
2017-11-29 16:55                                           ` [Cake] Fwd: " Georgios Amanakis
2017-11-29  3:42           ` [Cake] " Georgios Amanakis
2017-11-29  8:19             ` Pete Heist
2017-11-29 12:07               ` Pete Heist

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/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6F2894AD-87EA-4EFC-918E-625E49EDA977@gmail.com \
    --to=peteheist@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave@taht.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