I managed to do some network tests.
I found that no matter what cable or network port, the network on the
RPi4 always takes longer  than the Rpi3 at boot time to do whatever it's
waiting for (maybe DHCP renew?), entries always look like this:

Waiting for network................ Done (16).

After that I did some iperf tests and was surprised to see that the max
I could obtain was 300Mbps.
Lots of swapping cables, ports etc. later  could not get this to change,
and it matches what the Rpi3 can do.
I was using iperf in Receive mode using TCP on all clients.


Code:
--------------------
    
  [ WARN ] Squeezelite is running, results might be affected
  [ WARN ] Goto Main menu and stop squeezelite
  [ INFO ] Iperf running in TCP Mode.
  [ INFO ] Iperf running in Receive Mode.
  [ INFO ] Iperf will run for 20 seconds, then output will show.......
  iperf 3.6
  Linux PCP-XLR 4.19.122-pcpCore_v8 #1 SMP PREEMPT Tue May 26 20:10:39 EDT 2020 
aarch64
  Control connection MSS 1460
  Time: Tue, 30 Jun 2020 14:15:43 GMT
  Connecting to host 192.168.1.105, port 5201
  Reverse mode, remote host 192.168.1.105 is sending
  Cookie: ksidzafode2ewcqlwi7h6yxwfxp7buuetkev
  TCP MSS: 1460 (default)
  [  5] local 192.168.1.184 port 56022 connected to 192.168.1.105 port 5201
  Starting Test: protocol: TCP, 1 streams, 131072 byte blocks, omitting 0 
seconds, 20 second test, tos 0
  [ ID] Interval           Transfer     Bitrate
  [  5]   0.00-1.00   sec  34.2 MBytes   287 Mbits/sec                  
  [  5]   1.00-2.00   sec  36.3 MBytes   304 Mbits/sec                  
  [  5]   2.00-3.00   sec  36.1 MBytes   303 Mbits/sec                  
  [  5]   3.00-4.00   sec  36.3 MBytes   304 Mbits/sec                  
  [  5]   4.00-5.00   sec  35.3 MBytes   296 Mbits/sec                  
  [  5]   5.00-6.00   sec  35.6 MBytes   299 Mbits/sec                  
  [  5]   6.00-7.00   sec  34.1 MBytes   286 Mbits/sec                  
  [  5]   7.00-8.00   sec  37.5 MBytes   314 Mbits/sec                  
  [  5]   8.00-9.00   sec  35.2 MBytes   295 Mbits/sec                  
  [  5]   9.00-10.00  sec  35.3 MBytes   296 Mbits/sec                  
  [  5]  10.00-11.00  sec  36.6 MBytes   307 Mbits/sec                  
  [  5]  11.00-12.00  sec  34.9 MBytes   293 Mbits/sec                  
  [  5]  12.00-13.00  sec  35.2 MBytes   296 Mbits/sec                  
  [  5]  13.00-14.00  sec  37.5 MBytes   314 Mbits/sec                  
  [  5]  14.00-15.00  sec  36.0 MBytes   302 Mbits/sec                  
  [  5]  15.00-16.00  sec  35.6 MBytes   299 Mbits/sec                  
  [  5]  16.00-17.00  sec  34.8 MBytes   291 Mbits/sec                  
  [  5]  17.00-18.00  sec  35.5 MBytes   298 Mbits/sec                  
  [  5]  18.00-19.00  sec  37.1 MBytes   311 Mbits/sec                  
  [  5]  19.00-20.00  sec  34.3 MBytes   288 Mbits/sec                  
  - - - - - - - - - - - - - - - - - - - - - - - - -
  Test Complete. Summary Results:
  [ ID] Interval           Transfer     Bitrate
  [  5]   0.00-20.00  sec   714 MBytes   299 Mbits/sec                  sender
  [  5]   0.00-20.00  sec   713 MBytes   299 Mbits/sec                  receiver
  CPU Utilization: local/receiver 24.7% (2.6%u/22.2%s), remote/sender 0.1% 
(0.0%u/0.1%s)
  rcv_tcp_congestion cubic
  
  iperf Done.
  
--------------------
                

I was using two different Windows target machines, and between them they
can do GigE fine.

Also I can't seem to find anything that will show what the LAN port
speed is, ifconfig doesn't say and ethtool isn't present.
Ifconfig did show there were no packet errors, however.

Then I tried the iperf cmd via the cli directly, and got GigE speed!


Code:
--------------------
    
  $ iperf3 -c 192.168.1.105
  Connecting to host 192.168.1.105, port 5201
  [  5] local 192.168.1.184 port 56030 connected to 192.168.1.105 port 5201
  [ ID] Interval           Transfer     Bitrate         Retr  Cwnd
  [  5]   0.00-1.00   sec   109 MBytes   913 Mbits/sec    0    217 KBytes
  [  5]   1.00-2.00   sec   108 MBytes   908 Mbits/sec    0    217 KBytes
  [  5]   2.00-3.00   sec   107 MBytes   898 Mbits/sec    0    217 KBytes
  [  5]   3.00-4.00   sec   110 MBytes   921 Mbits/sec    0    217 KBytes
  [  5]   4.00-5.00   sec   109 MBytes   912 Mbits/sec    0    217 KBytes
  [  5]   5.00-6.00   sec   108 MBytes   904 Mbits/sec    0    217 KBytes
  [  5]   6.00-7.00   sec   107 MBytes   901 Mbits/sec    0    217 KBytes
  [  5]   7.00-8.00   sec   110 MBytes   920 Mbits/sec    0    217 KBytes
  [  5]   8.00-9.00   sec   109 MBytes   911 Mbits/sec    0    217 KBytes
  [  5]   9.00-10.00  sec   109 MBytes   916 Mbits/sec    0    217 KBytes
  - - - - - - - - - - - - - - - - - - - - - - - - -
  [ ID] Interval           Transfer     Bitrate         Retr
  [  5]   0.00-10.00  sec  1.06 GBytes   910 Mbits/sec    0             sender
  [  5]   0.00-10.00  sec  1.06 GBytes   910 Mbits/sec                  receiver
  
  iperf Done.
  
--------------------


So at least the port speed and perf is fine now, but what is the diff
between the UI and CLI iperf cmds that's causing the speed diff?


------------------------------------------------------------------------
mr-b's Profile: http://forums.slimdevices.com/member.php?userid=10044
View this thread: http://forums.slimdevices.com/showthread.php?t=112456

_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/unix

Reply via email to