Date: Tue, 22 Jun 2021 21:56:08 -0700 From: Mark Millard via freebsd-arm <freebsd-arm@freebsd.org> To: MJ <mafsys1234@gmail.com> Cc: Ronald Klop <ronald-lists@klop.ws>, freebsd-arm@freebsd.org Subject: Re: Raspberry Pi 3B+ and pitiful network speeds Message-ID: <38222A46-5FCC-4E74-BC7F-21C4D2FB2DDF@yahoo.com> In-Reply-To: <1f13faa0-3f87-f3d2-0289-9579f33df8d0@gmail.com> References: <fcd91ac5-c807-3409-d1b6-a41ba6fdc362@gmail.com> <20210620144513.1f91a68f@basepc> <169baf0b-3f3c-f1dc-4a6f-b8a0ef863f51@denninger.net> <20210620154105.0c83bbcc@basepc> <20210620222922.51da1818@basepc> <3fa3f2a6-8560-f413-b2eb-5c172ce025eb@gmail.com> <6B4F2FB6-ABA1-4CFA-BE2A-6A466C30FF02@yahoo.com> <fa37f5ef-09e1-f5a2-90c0-102f3af7aa92@gmail.com> <20210621111301.75fa1c7a@basepc> <ae290aa3-b28c-a48d-8d1e-61d253a150eb@gmail.com> <1880280342.34.1624368348439@localhost> <1f13faa0-3f87-f3d2-0289-9579f33df8d0@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2021-Jun-22, at 19:18, MJ <mafsys1234 at gmail.com> wrote:
> On 22/06/2021 11:25 pm, Ronald Klop wrote:
>> <...>
>=20
>>=20
>> Hi,
>>=20
>> Just another data point for the investigation.
>>=20
>> RPI3B+ FreeBSD 13.0-RELEASE-p1 #0: Wed May 26 22:19:21 UTC 2021 =
GENERIC
>> ue0: flags=3D8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> =
metric 0 mtu 1500
>> options=3D80009<RXCSUM,VLAN_MTU,LINKSTATE>
>> ether b8:27:xx:xx:xx:xx
>> inet 192.168.1.148 netmask 0xffffff00 broadcast 192.168.1.255
>> media: Ethernet autoselect (1000baseT <full-duplex>)
>> status: active
>> nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
>>=20
>>=20
>> RPI4 FreeBSD 14.0-CURRENT #7 main-62ffcaab8: Tue Mar 23 17:26:53 CET =
2021 GENERIC-NODEBUG
>> genet0: flags=3D8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> =
metric 0 mtu 1500
>> options=3D280009<RXCSUM,VLAN_MTU,LINKSTATE,RXCSUM_IPV6>
>> ether dc:a6:xx:xx:xx:xx
>> inet 192.168.1.127 netmask 0xffffff00 broadcast 192.168.1.255
>> media: Ethernet autoselect (1000baseT <full-duplex,master>)
>> status: active
>> nd6 options=3D29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
>>=20
>>=20
>> These two are next to each other connected by a 1gbit switch.
>>=20
>>=20
>> [root@rpi3 ~]# iperf -c rpi4 -w 2m -t 30s -i 1
>> ------------------------------------------------------------
>> Client connecting to rpi4, TCP port 5001
>> TCP window size: 32.8 KByte (WARNING: requested 1.91 MByte)
>> ------------------------------------------------------------
>> [ 1] local 192.168.1.148 port 21246 connected with 192.168.1.127 =
port 5001
>> [ ID] Interval Transfer Bandwidth
>> [ 1] 0.00-1.00 sec 12.6 MBytes 106 Mbits/sec
>> [ 1] 1.00-2.00 sec 13.6 MBytes 114 Mbits/sec
>> [ 1] 2.00-3.00 sec 13.5 MBytes 113 Mbits/sec
>> [ 1] 3.00-4.00 sec 13.6 MBytes 114 Mbits/sec
>> [ 1] 4.00-5.00 sec 13.5 MBytes 113 Mbits/sec
>> [ 1] 5.00-6.00 sec 13.6 MBytes 114 Mbits/sec
>> [ 1] 6.00-7.00 sec 13.6 MBytes 114 Mbits/sec
>> [ 1] 7.00-8.00 sec 13.6 MBytes 114 Mbits/sec
>> [ 1] 8.00-9.00 sec 13.2 MBytes 111 Mbits/sec
>> [ 1] 9.00-10.00 sec 13.5 MBytes 113 Mbits/sec
>>=20
>>=20
>> [root@rpi4 ~]# iperf -c rpi3 -w 2m -t 30s -i 1
>> ------------------------------------------------------------
>> Client connecting to rpi3, TCP port 5001
>> TCP window size: 32.8 KByte (WARNING: requested 1.91 MByte)
>> ------------------------------------------------------------
>> [ 1] local 192.168.1.127 port 24993 connected with 192.168.1.148 =
port 5001
>> [ ID] Interval Transfer Bandwidth
>> [ 1] 0.00-1.00 sec 15.6 MBytes 131 Mbits/sec
>> [ 1] 1.00-2.00 sec 16.8 MBytes 141 Mbits/sec
>> [ 1] 2.00-3.00 sec 16.6 MBytes 139 Mbits/sec
>> [ 1] 3.00-4.00 sec 16.8 MBytes 141 Mbits/sec
>> [ 1] 4.00-5.00 sec 16.5 MBytes 138 Mbits/sec
>> [ 1] 5.00-6.00 sec 16.8 MBytes 141 Mbits/sec
>> [ 1] 6.00-7.00 sec 16.4 MBytes 137 Mbits/sec
>> [ 1] 7.00-8.00 sec 16.5 MBytes 138 Mbits/sec
>> [ 1] 8.00-9.00 sec 16.6 MBytes 139 Mbits/sec
>> [ 1] 9.00-10.00 sec 14.6 MBytes 123 Mbits/sec
>>=20
>>=20
>> Regards,
>> Ronald.
>>=20
> These are very poor for the RPI4, are they not? Is it not fully =
1000Mbit?
In both of the above tests, the RPi3B+ is either the sender
or the receiver: always involved. That likely bottlenecks
the RPi4B.
For reference:
QUOTE from "man iperf3"
Normally, the test data is sent from the client to the server, and
measures the upload speed of the client. Measuring the download =
speed
from the server can be done by specifying the -R flag on the =
client.
END QUOTE
I'll note that the -w 2m was ineffective: 32.8KByte was used.
> Your RPI3B results are a little better than mine. They are still not =
very impressive though.
In essence the tests confirm the trend of your results --but
from a different context.
=3D=3D=3D
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38222A46-5FCC-4E74-BC7F-21C4D2FB2DDF>