Historic archive of defunct list mab-wifi@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: mab-wifi@lists.bufferbloat.net
Subject: [mab-wifi] Initial algorithm simulation results
Date: Mon, 06 Mar 2017 13:43:09 +0100	[thread overview]
Message-ID: <87mvcyshia.fsf@alrua-kau> (raw)

[-- Attachment #1: Type: text/plain, Size: 1695 bytes --]

So I've finally gotten around to trying out the Python bandit algorithm
implementations from
https://www.math.univ-toulouse.fr/~agarivie/Telecom/bandits/

I have added a very simple WiFi arm implementation to the code base
(which is basically a Bernoulli arm that succeeds with a certain
probability and gives a payoff scaled by the base rate), which can be
instantiated from the rate_stats_csv output from Minstrel in the kernel.

Based on the data from a simple test run in my own testbed I was able to
get three of the algorithms to produce something meaningful; see the
attached graph. The best of the algorithms performs roughly comparable
to Minstrel (I think; the numbers are not quite straight forward to
compare).

I have not been able to get the Thompson and BayesUCB algorithms to work
with this scenario yet (they require a posterior distribution to sample
from, and the included implementation doesn't work with the varying
payoffs of each arm). However, perhaps sticking with the KL-UCB
algorithm is better anyway (same one the "optimal rate sampling"
modifies; haven't quite grokked how they modify it yet).

Anyway, I do believe it is possible to extend this simulation to
something that we can use to guide, say, a dynamic implementation (i.e.,
change the probabilities over the duration of the test run), as well as
evaluating the effects of collapsing arms / defining them differently.
It would probably be good with a better source of the actual
probabilities for each rate, though.

So yeah, bit of a brain dump of where I'm at; but I'll be away for the
next couple of weeks, so though it better to get this out there.

Code here: https://kau.toke.dk/git/pybandits/

-Toke


[-- Attachment #2: initial-wifi.png --]
[-- Type: image/png, Size: 43579 bytes --]

             reply	other threads:[~2017-03-06 12:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06 12:43 Toke Høiland-Jørgensen [this message]
     [not found] ` <CAGp19xdZtvDXXNuo7g8tU52-pPWSL0k4QT8Z8-px3OcACU_Qyw@mail.gmail.com>
2017-03-12 19:35   ` Toke Høiland-Jørgensen
     [not found]     ` <CAGp19xf7B0QA+Js6fWV2CN_=-2L9N2rVC-p=ph6kBWUu=LsbXg@mail.gmail.com>
2017-04-20 22:16       ` Björn Smedman

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

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

  git send-email \
    --in-reply-to=87mvcyshia.fsf@alrua-kau \
    --to=toke@toke.dk \
    --cc=mab-wifi@lists.bufferbloat.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