From: "Кирилл Луконин" <klukonin@gmail.com>
To: Marek Lindner <mareklindner@neomailbox.ch>
Cc: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [PATCH] batman-adv: Use wifi rx/tx as fallback throughput
Date: Thu, 27 Jun 2019 15:41:54 +0500 [thread overview]
Message-ID: <CALYz8ypn2fQYCxbFDCbUmAgYHcHaxzPgGWkQPAhz2qxy3Qu-RA@mail.gmail.com> (raw)
In-Reply-To: <2561263.F3lYGfnSHf@rousseau>
Hello, Marek.
On Thursday, 13 June 2019 04:50:44 HKT Кирилл Луконин wrote:
>> So here is the algorithm. It has a structure we call matryoshka.
>> ET - Expected_throughput.
>>
>> 1) ET = TX_bitrate * Transmit_probability * Overhead_coefficient
>> Transmit_probability is always less than 1 so Expected throughput
>> can't be equal to the TX_bitrate. Overhead_coefficient is also should
>> be less than 1
>>
>> 2) Transmit_probability = 1 - Retry_probability - Error_probability
>>
>> 3) Retry_probability = TX_retries / TX_packets
>>
>> 4) Error_probability = TX_errors / TX_packets
>>
>> 5) Overhead_coefficient for 802.11 is fair enough to be 0.65, but can
>> be changed after additional testing.
>>
>>
>> ET = TX_bitrate * (1 - (TX_retries + TX_errors) / TX_packets) * 0.65
>> Such technique has very large hysteresis which is good to avoid
>> flapping between different nodes.
>> In my MESH lab this formula works quite well.
>This looks like an interesting approach. Which chips / environments did you
>test this formula with and how did the result compare to the actual TCP
>throughput ?
>Thanks,
>Marek
Mostly QCA988x was tested.
Sorry, I lost my test results so I need to do it again.
I have UBNT AC MESH, UBNT AP AC Lite and TP-Link RE450 in my lab.
Also, as I think, it's better to test UDP throughput, But I can test
both TCP and UDP.
This formula always show a result that close to UDP throughput. So,
may be we can think about additional parameters/coefficients that
depend on protocols or something else.
Best Regards,
Lukonin Kirill
вт, 25 июн. 2019 г. в 13:26, Marek Lindner <mareklindner@neomailbox.ch>:
>
> On Thursday, 13 June 2019 04:50:44 HKT Кирилл Луконин wrote:
> > So here is the algorithm. It has a structure we call matryoshka.
> > ET - Expected_throughput.
> >
> > 1) ET = TX_bitrate * Transmit_probability * Overhead_coefficient
> > Transmit_probability is always less than 1 so Expected throughput
> > can't be equal to the TX_bitrate. Overhead_coefficient is also should
> > be less than 1
> >
> > 2) Transmit_probability = 1 - Retry_probability - Error_probability
> >
> > 3) Retry_probability = TX_retries / TX_packets
> >
> > 4) Error_probability = TX_errors / TX_packets
> >
> > 5) Overhead_coefficient for 802.11 is fair enough to be 0.65, but can
> > be changed after additional testing.
> >
> >
> > ET = TX_bitrate * (1 - (TX_retries + TX_errors) / TX_packets) * 0.65
> > Such technique has very large hysteresis which is good to avoid
> > flapping between different nodes.
> > In my MESH lab this formula works quite well.
>
> This looks like an interesting approach. Which chips / environments did you
> test this formula with and how did the result compare to the actual TCP
> throughput ?
>
> Thanks,
> Marek
>
next prev parent reply other threads:[~2019-06-27 10:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 10:19 [PATCH] batman-adv: Use wifi rx/tx as fallback throughput René Treffer
2019-06-09 10:37 ` Sven Eckelmann
2019-06-09 11:40 ` Marek Lindner
2019-06-09 12:45 ` René Treffer
2019-06-10 3:31 ` Marek Lindner
2019-06-10 7:37 ` Кирилл Луконин
2019-06-12 6:39 ` Marek Lindner
2019-06-12 20:50 ` Кирилл Луконин
2019-06-25 8:26 ` Marek Lindner
2019-06-27 10:41 ` Кирилл Луконин [this message]
2019-06-27 10:57 ` Marek Lindner
2019-06-10 10:06 ` René Treffer
2019-08-11 12:50 ` Marek Lindner
[not found] ` <CALD2-cLnviLCav=Lui9T4Mzz1nnY93kN_0ypd-nhwFUhKNYRQg@mail.gmail.com>
2019-08-11 13:17 ` Marek Lindner
2019-06-09 10:41 ` Sven Eckelmann
2019-06-09 11:09 ` Sven Eckelmann
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=CALYz8ypn2fQYCxbFDCbUmAgYHcHaxzPgGWkQPAhz2qxy3Qu-RA@mail.gmail.com \
--to=klukonin@gmail.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=mareklindner@neomailbox.ch \
/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;
as well as URLs for NNTP newsgroup(s).