From: Antonio Quartulli <ordex@autistici.org>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] batctl bw performance
Date: Fri, 7 Jun 2013 19:27:34 +0200 [thread overview]
Message-ID: <20130607172734.GO1789@ritirata.org> (raw)
In-Reply-To: <51B214AE.2090603@inti.gob.ar>
[-- Attachment #1: Type: text/plain, Size: 4199 bytes --]
Hello Gabriel,
On Fri, Jun 07, 2013 at 02:13:18PM -0300, Gabriel Tolón wrote:
>
> This time, I logged just from Equipo 1, to generate less traffic.
>
> I noticed something weird. When I run batctl bw I get this time
> something like 12 Mbps. If I wait for about 10 seconds and repeat the
> command, I get something similar, but, if I run the command inmediatly
> after the bw test finishes, the result improves a lot, here you can see
> the commands with the seconds between them:
>
>
> root@Equipo 1:~# date; batctl bw -t 2000 E3-5GHz
> Fri Jun 7 16:40:09 UTC 2013
> Bandwidth meter called towards 64:70:02:4e:d9:d7
> Test over in 2000ms.
> Sent 3064500 Bytes.
> Throughput: 1.46 MB/s (12.26 Mbps)
> root@Equipo 1:~#
> root@Equipo 1:~#
> root@Equipo 1:~# date; batctl bw -t 2000 E3-5GHz
> Fri Jun 7 16:40:15 UTC 2013
> Bandwidth meter called towards 64:70:02:4e:d9:d7
> Test over in 2000ms.
> Sent 3201000 Bytes.
> Throughput: 1.53 MB/s (12.80 Mbps)
> root@Equipo 1:~#
> root@Equipo 1:~#
> root@Equipo 1:~# date; batctl bw -t 2000 E3-5GHz
> Fri Jun 7 16:40:18 UTC 2013
> Bandwidth meter called towards 64:70:02:4e:d9:d7
> Test over in 2000ms.
> Sent 14545500 Bytes.
> Throughput: 6.94 MB/s (58.18 Mbps)
> root@Equipo 1:~#
> root@Equipo 1:~# date; batctl bw -t 2000 E3-5GHz
> Fri Jun 7 16:40:20 UTC 2013
> Bandwidth meter called towards 64:70:02:4e:d9:d7
> Test over in 2000ms.
> Sent 18729000 Bytes.
> Throughput: 8.93 MB/s (74.91 Mbps)
> root@Equipo 1:~#
> root@Equipo 1:~# date; batctl bw -t 2000 E3-5GHz
> Fri Jun 7 16:40:23 UTC 2013
> Bandwidth meter called towards 64:70:02:4e:d9:d7
> Test over in 2000ms.
> Sent 21067500 Bytes.
> Throughput: 10.05 MB/s (84.26 Mbps)
> root@Equipo 1:~#
> root@Equipo 1:~# date; batctl bw -t 2000 E3-5GHz
> Fri Jun 7 16:40:26 UTC 2013
> Bandwidth meter called towards 64:70:02:4e:d9:d7
> Test over in 2000ms.
> Sent 22351500 Bytes.
> Throughput: 10.66 MB/s (89.40 Mbps)
> root@Equipo 1:~#
> root@Equipo 1:~# date; batctl bw -t 2000 E3-5GHz
> Fri Jun 7 16:40:37 UTC 2013
> Bandwidth meter called towards 64:70:02:4e:d9:d7
> Test over in 2000ms.
> Sent 13281000 Bytes.
> Throughput: 6.33 MB/s (53.12 Mbps)
> root@Equipo 1:~#
> root@Equipo 1:~#
> root@Equipo 1:~#
> root@Equipo 1:~# date; batctl bw -t 2000 E3-5GHz
> Fri Jun 7 16:40:49 UTC 2013
> Bandwidth meter called towards 64:70:02:4e:d9:d7
> Test over in 2000ms.
> Sent 3204000 Bytes.
> Throughput: 1.53 MB/s (12.82 Mbps)
> root@Equipo 1:~#
>
>
> Maybe something in the time calculation is wrong?
>
This strange. The point is that the receiver takes at least 1 second to shutdown
the session. Theoretically (and this is what happened during my tests) the
receiver should refuse any "second new" connection and the sender should then
get 0 throughput. Can I ask you what wifi driver is your device using?
Anyway, there must be something wrong in the bw meter given that you see this
behaviour only with it and not with iperf.
Did you try a short run over Ethernet? I'm curious to see if the behaviour will
be the same.
> The logs aretoo heavy for pastebin, so here it's just the part
> corresponding to the first batctl bw in Equipo1:
>
> http://pastebin.com/THEr2Cq3
>
Thanks for the log.
I saw something strange:
16:40:09.533172 BAT 64:70:02:4e:d9:43 > E3-5GHz: ICMP BW type MSG (0), id 0, seq
2018499, ttl 50, v 15, length 1510
16:40:09.533392 BAT 64:70:02:4e:d9:43 > E3-5GHz: ICMP BW type MSG (0), id 0, seq
2049999, ttl 50, v 15, length 1510
These are two packets sent one after the other but the second sequence number is
not equal to the first + 1500 (payload size)
> If you want to watch the whole log I can send you, or paste it in parts.
>
This gave me already some hints. I'll dig into the code to try to spot what's
wrong. But strange that I did not see any problem during my tests..maybe
something introduced later by accident.
Thank you so far. I'm still curious about the Ethernet test, then I'll try to
upload some more code to test :)
Cheers,
--
Antonio Quartulli
..each of us alone is worth nothing..
Ernesto "Che" Guevara
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-06-07 17:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51A3C7E9.7080208@inti.gob.ar>
[not found] ` <20130528070057.GC3333@ritirata.org>
[not found] ` <51ACBCE4.8000506@inti.gob.ar>
2013-06-03 16:08 ` [B.A.T.M.A.N.] batctl bw performance Antonio Quartulli
2013-06-03 20:54 ` Gabriel Tolón
2013-06-04 5:13 ` Antonio Quartulli
2013-06-04 5:38 ` Antonio Quartulli
2013-06-05 15:17 ` Gabriel Tolón
2013-06-05 15:27 ` Gabriel Tolón
2013-06-06 5:51 ` Antonio Quartulli
2013-06-06 18:19 ` Gabriel Tolón
2013-06-06 18:29 ` Antonio Quartulli
2013-06-06 19:04 ` Gabriel Tolón
2013-06-06 19:18 ` Antonio Quartulli
2013-06-07 13:49 ` Gabriel Tolón
2013-06-07 13:57 ` Antonio Quartulli
2013-06-07 14:38 ` Gabriel Tolón
2013-06-07 14:40 ` Antonio Quartulli
2013-06-07 17:13 ` Gabriel Tolón
2013-06-07 17:27 ` Antonio Quartulli [this message]
2013-06-07 18:39 ` Antonio Quartulli
2013-06-07 18:57 ` Gabriel Tolón
2013-06-08 12:29 ` Antonio Quartulli
2013-06-08 20:20 ` Antonio Quartulli
2013-06-09 0:26 ` NicoEchániz
2013-06-10 13:12 ` Gabriel Tolón
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=20130607172734.GO1789@ritirata.org \
--to=ordex@autistici.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/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