I installed a fresh Raspbian (PIXEL), and have it connected to a router via the Ethernet port. Why is the network performance so miserable? At most I can get about 10kb per second. Even typing in command lines involves waiting several seconds for keystrokes to appear. This is not a problem on any other machine, just the pi.
[EDIT 3/19/17: Just replaced my router and these problems with internal LAN performance went away. The pi now gets 90-100 Mbits/s.]
Insanely slow network performance
Last edited by jtiscione on Mon Mar 20, 2017 2:02 am, edited 1 time in total.
Re: Insanely slow network performance
You have a problem in the network configuration, this can be hardware and/or software.jtiscione wrote:I installed a fresh Raspbian (PIXEL), and have it connected to a router via the Ethernet port. Why is the network performance so miserable? At most I can get about 10kb per second. Even typing in command lines involves waiting several seconds for keystrokes to appear. This is not a problem on any other machine, just the pi.
Why are the Raspberry Pi's network capabilities so atrocious?
If you need help then please give more information, like what Pi, which OS release, network configuration, active interfaces, system activity.
Btw. I get 9MByte/sec to a Pi 3.
The road to insanity is paved with static ip addresses
Re: Insanely slow network performance
They are not, you are blaming the Pi for something when it is not its fault. Don't you think that if the Pi was this bad people would have noticed? So there is an issue with you network setup, and to diagnose that more information is needed.jtiscione wrote:I installed a fresh Raspbian (PIXEL), and have it connected to a router via the Ethernet port. Why is the network performance so miserable? At most I can get about 10kb per second. Even typing in command lines involves waiting several seconds for keystrokes to appear. This is not a problem on any other machine, just the pi.
Why are the Raspberry Pi's network capabilities so atrocious?
Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Contrary to popular belief, humorous signatures are allowed.
I've been saying "Mucho" to my Spanish friend a lot more lately. It means a lot to him.
Contrary to popular belief, humorous signatures are allowed.
I've been saying "Mucho" to my Spanish friend a lot more lately. It means a lot to him.
Re: Insanely slow network performance
You can get up to around:-
Code: Select all
$ iperf -c pi3
------------------------------------------------------------
Client connecting to pi, TCP port 5001
TCP window size: 85.0 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.0.8 port 48526 connected with 192.168.0.80 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.0 sec 382 MBytes 320 Mbits/sec
Re: Insanely slow network performance
How did you do that? It is supposed to be difficult to get past 100M as the ethernet on Pi is only 100M.jahboater wrote:You can get up to around:-Code: Select all
$ iperf -c pi3 ------------------------------------------------------------ Client connecting to pi, TCP port 5001 TCP window size: 85.0 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.0.8 port 48526 connected with 192.168.0.80 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 382 MBytes 320 Mbits/sec
I get
Code: Select all
$ iperf -c pi10
------------------------------------------------------------
Client connecting to pi10, TCP port 5001
TCP window size: 85.0 KByte (default)
------------------------------------------------------------
[ 3] local 192.168.254.229 port 47067 connected with 192.168.254.107 port 5001
[ ID] Interval Transfer Bandwidth
[ 3] 0.0-10.1 sec 116 MBytes 96.4 Mbits/sec
Re: Insanely slow network performance
Sorry, thats with a USB adapter. Your figure is about right for the built-in ethernet.shuckle wrote: I get(My test linux and pi3 are on the same 1G switch.)Code: Select all
$ iperf -c pi10 ------------------------------------------------------------ Client connecting to pi10, TCP port 5001 TCP window size: 85.0 KByte (default) ------------------------------------------------------------ [ 3] local 192.168.254.229 port 47067 connected with 192.168.254.107 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 116 MBytes 96.4 Mbits/sec
I was just showing what the Pi is actually capable of.
Re: Insanely slow network performance
This is a pi 3, with Raspbian PIXEL. As for "network configuration", "active interfaces", and "system activity", I'm not sure what you're asking for. The network configuration is Ethernet, plugged in to a standard router from an ISP.Ernst wrote:If you need help then please give more information, like what Pi, which OS release, network configuration, active interfaces, system activity.
Re: Insanely slow network performance
Yes, I figure people would have noticed, and the fact that no one else is reporting this is what made me come here to ask. Everyone complaining about slow network performance is still reporting speeds that are still 10-100X what I'm seeing.jamesh wrote:They are not, you are blaming the Pi for something when it is not its fault. Don't you think that if the Pi was this bad people would have noticed? So there is an issue with you network setup, and to diagnose that more information is needed.
Re: Insanely slow network performance
This is what I'm seeing-
Actually that's not as slow as I thought it was, but it's still pretty bad. I'm not sure where to start looking though.
Code: Select all
Connecting to host 192.168.0.24, port 5201
[ 4] local 192.168.0.10 port 51899 connected to 192.168.0.24 port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 223 KBytes 1.83 Mbits/sec
[ 4] 1.00-2.00 sec 75.7 KBytes 620 Kbits/sec
[ 4] 2.00-3.00 sec 33.9 KBytes 277 Kbits/sec
[ 4] 3.00-4.00 sec 0.00 Bytes 0.00 bits/sec
[ 4] 4.00-5.00 sec 2.83 KBytes 23.2 Kbits/sec
[ 4] 5.00-6.00 sec 4.24 KBytes 34.8 Kbits/sec
[ 4] 6.00-7.00 sec 63.6 KBytes 522 Kbits/sec
[ 4] 7.00-8.00 sec 320 KBytes 2.62 Mbits/sec
[ 4] 8.00-9.00 sec 99.0 KBytes 810 Kbits/sec
[ 4] 9.00-10.00 sec 42.2 KBytes 345 Kbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 865 KBytes 708 Kbits/sec sender
[ 4] 0.00-10.00 sec 737 KBytes 603 Kbits/sec receiver
Re: Insanely slow network performance
What adaptor are you using?jahboater wrote:Sorry, thats with a USB adapter. Your figure is about right for the built-in ethernet.
I was just showing what the Pi is actually capable of.
Re: Insanely slow network performance
Please enter the following commands from the command line/terminal:jtiscione wrote:This is a pi 3, with Raspbian PIXEL. As for "network configuration", "active interfaces", and "system activity", I'm not sure what you're asking for. The network configuration is Ethernet, plugged in to a standard router from an ISP.Ernst wrote:If you need help then please give more information, like what Pi, which OS release, network configuration, active interfaces, system activity.
Code: Select all
man uname
man ifconfig
man route
Code: Select all
uname -a
ifconfig -a
route
dhcpcd -U eth0
dhcpcd -U wlan0
The road to insanity is paved with static ip addresses
Re: Insanely slow network performance
Entering uname -a generates:Ernst wrote:Code: Select all
uname -a ifconfig -a route dhcpcd -U eth0 dhcpcd -U wlan0
Linux raspberrypi 4.4.38-v7+ #938 SMP Thu Dec 15 15:22:21 GMT 2016 armv7l GNU/Linux
ifconfig -a :
Code: Select all
eth0 Link encap:Ethernet HWaddr b8:27:eb:d8:75:5c
inet addr:192.168.0.24 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::5bb6:b847:6e61:1d11/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14289301 errors:0 dropped:684 overruns:0 frame:0
TX packets:13701734 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2000635982 (1.8 GiB) TX bytes:2993440958 (2.7 GiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:96680 errors:0 dropped:0 overruns:0 frame:0
TX packets:96680 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:6114754 (5.8 MiB) TX bytes:6114754 (5.8 MiB)
wlan0 Link encap:Ethernet HWaddr b8:27:eb:8d:20:09
inet addr:192.168.0.99 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::f55c:b69a:61ec:f566/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2574236 errors:0 dropped:173601 overruns:0 frame:0
TX packets:7915 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:460699818 (439.3 MiB) TX bytes:991117 (967.8 KiB)
Code: Select all
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default modem.Home 0.0.0.0 UG 202 0 0 eth0
default modem.Home 0.0.0.0 UG 303 0 0 wlan0
192.168.0.0 * 255.255.255.0 U 202 0 0 eth0
192.168.0.0 * 255.255.255.0 U 303 0 0 wlan0
Code: Select all
broadcast_address='192.168.0.255'
dhcp_lease_time='86400'
dhcp_message_type='5'
dhcp_server_identifier='192.168.0.1'
domain_name='Home'
domain_name_servers='192.168.0.1 205.171.3.25'
ip_address='192.168.0.24'
network_number='192.168.0.0'
routers='192.168.0.1'
subnet_cidr='24'
subnet_mask='255.255.255.0'
Re: Insanely slow network performance
Did you have a look the output ?
I can see at least three or more problem.
I suggest you start with reading the ifconfig output for wlan0
I can see at least three or more problem.
I suggest you start with reading the ifconfig output for wlan0
The road to insanity is paved with static ip addresses
Re: Insanely slow network performance
What 3 problems? What's interesting about the output from ifconfig wlan0?
Re: Insanely slow network performance
You were able to decide that the pi network capabilities so atrocious but you are unable to notice the problems in your network. May I remind you that the the Pi is about learning and this is something you have to do for yourself, we are just here to assist you when needed.
Did you notice the following line ?
RX packets:2574236 errors:0 dropped:173601 overruns:0 frame:0
This is a 6% failure rate on your wifi, this must not be important but it is something that may need attention, normally the next that would be noticed is the same line under eth0:
RX packets:14289301 errors:0 dropped:684 overruns:0 frame:0
Better, can be ignored at this low rate.
What is more important are the following two lines:
eth0: inet addr:192.168.0.24 Bcast:192.168.0.255 Mask:255.255.255.0
wlan0: inet addr:192.168.0.99 Bcast:192.168.0.255 Mask:255.255.255.0
This is not good, either disable one interface or use a different subnet.
The reason can be seen below:
As you can see above you have two routes into the same network, but the first route has a lower metric (=higher priority). Under unfavorable conditions(*) it may happen that traffic is routed over both interfaces so that the slowest interface reduces the performance.
(*) What is the operating system on the other machine used with iperf ? How many network interfaces does this system have ?
I suggest you disable and/or remove the wlan0 interface and try again.
Did you notice the following line ?
RX packets:2574236 errors:0 dropped:173601 overruns:0 frame:0
This is a 6% failure rate on your wifi, this must not be important but it is something that may need attention, normally the next that would be noticed is the same line under eth0:
RX packets:14289301 errors:0 dropped:684 overruns:0 frame:0
Better, can be ignored at this low rate.
What is more important are the following two lines:
eth0: inet addr:192.168.0.24 Bcast:192.168.0.255 Mask:255.255.255.0
wlan0: inet addr:192.168.0.99 Bcast:192.168.0.255 Mask:255.255.255.0
This is not good, either disable one interface or use a different subnet.
The reason can be seen below:
Code: Select all
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default modem.Home 0.0.0.0 UG 202 0 0 eth0
default modem.Home 0.0.0.0 UG 303 0 0 wlan0
192.168.0.0 * 255.255.255.0 U 202 0 0 eth0
192.168.0.0 * 255.255.255.0 U 303 0 0 wlan0
(*) What is the operating system on the other machine used with iperf ? How many network interfaces does this system have ?
I suggest you disable and/or remove the wlan0 interface and try again.
The road to insanity is paved with static ip addresses
Re: Insanely slow network performance
Ernst- Sorry if I gave the wrong impression with the original post. I was referring to this particular pi on my network, not meaning to insult all raspberry pis in general. This is not the pi's "fault", it's obviously the network, but among the machines here I only had this problem on the pi.You were able to decide that the pi network capabilities so atrocious but you are unable to notice the problems in your network. May I remind you that the the Pi is about learning and this is something you have to do for yourself, we are just here to assist you when needed.
But disabling wlan0 now gives me from iperf3
Code: Select all
Accepted connection from 192.168.0.10, port 53704
[ 5] local 192.168.0.24 port 5201 connected to 192.168.0.10 port 53705
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-1.00 sec 4.78 MBytes 40.1 Mbits/sec
[ 5] 1.00-2.00 sec 5.21 MBytes 43.7 Mbits/sec
[ 5] 2.00-3.00 sec 4.42 MBytes 37.1 Mbits/sec
[ 5] 3.00-4.00 sec 4.29 MBytes 36.0 Mbits/sec
[ 5] 4.00-5.00 sec 505 KBytes 4.14 Mbits/sec
[ 5] 5.00-6.00 sec 536 KBytes 4.39 Mbits/sec
[ 5] 6.00-7.00 sec 281 KBytes 2.31 Mbits/sec
[ 5] 7.00-8.00 sec 1.77 MBytes 14.8 Mbits/sec
[ 5] 8.00-9.00 sec 2.19 MBytes 18.4 Mbits/sec
[ 5] 9.00-10.00 sec 6.85 MBytes 57.4 Mbits/sec
[ 5] 10.00-10.02 sec 164 KBytes 75.4 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-10.02 sec 31.2 MBytes 26.1 Mbits/sec sender
[ 5] 0.00-10.02 sec 31.0 MBytes 25.9 Mbits/sec receiver
-Jason
Re: Insanely slow network performance
It has gotten better but still not good enough. There must be something else that is causing some problems because there is too much variation in your results. Just take a look at the following using a Pi3 on ethernet to a Pi 0 W, there are two ethernet switches between the Pi 3 and the access point, the Pi 0 W is one floor below the access point:
This time between two Pi 3
What you can see above is that there is a very little variance in the performance, your measurement shows a lot of variance:
There can be many reasons and it can be very difficult to find the cause as it can be anywhere in the network. The first item to check is the power supply, then the ethernet cable.If this does not bring up anything you will have check everything connected to find what could be causing the problems.
EDIT: Is the other system that you are using for iperf using a wireless interface ? In that case your measurement may make sense.
Code: Select all
pi@raspi3:~ $ iperf3 -c raspi4
Connecting to host raspi4, port 5201
[ 4] local 192.168.0.230 port 46512 connected to 192.168.0.235 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 4.54 MBytes 38.0 Mbits/sec 2 170 KBytes
[ 4] 1.00-2.00 sec 3.81 MBytes 32.0 Mbits/sec 0 182 KBytes
[ 4] 2.00-3.00 sec 4.62 MBytes 38.8 Mbits/sec 0 198 KBytes
[ 4] 3.00-4.00 sec 4.21 MBytes 35.4 Mbits/sec 0 214 KBytes
[ 4] 4.00-5.00 sec 3.91 MBytes 32.8 Mbits/sec 0 225 KBytes
[ 4] 5.00-6.00 sec 3.52 MBytes 29.5 Mbits/sec 0 257 KBytes
[ 4] 6.00-7.00 sec 4.24 MBytes 35.6 Mbits/sec 0 320 KBytes
[ 4] 7.00-8.00 sec 4.10 MBytes 34.4 Mbits/sec 0 404 KBytes
[ 4] 8.00-9.00 sec 4.67 MBytes 39.2 Mbits/sec 0 518 KBytes
[ 4] 9.00-10.00 sec 3.54 MBytes 29.6 Mbits/sec 0 645 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 41.2 MBytes 34.5 Mbits/sec 2 sender
[ 4] 0.00-10.00 sec 40.8 MBytes 34.2 Mbits/sec receiver
iperf Done.
Code: Select all
pi@raspi3:~ $ iperf3 -c raspi2
Connecting to host raspi2, port 5201
[ 4] local 192.168.0.230 port 33776 connected to 192.168.0.249 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 11.3 MBytes 94.6 Mbits/sec 0 35.4 KBytes
[ 4] 1.00-2.00 sec 11.2 MBytes 94.2 Mbits/sec 0 38.2 KBytes
[ 4] 2.00-3.00 sec 11.2 MBytes 94.1 Mbits/sec 0 39.6 KBytes
[ 4] 3.00-4.00 sec 11.2 MBytes 94.2 Mbits/sec 0 43.8 KBytes
[ 4] 4.00-5.00 sec 11.3 MBytes 94.4 Mbits/sec 0 59.4 KBytes
[ 4] 5.00-6.00 sec 11.2 MBytes 94.0 Mbits/sec 0 59.4 KBytes
[ 4] 6.00-7.00 sec 11.3 MBytes 94.4 Mbits/sec 0 59.4 KBytes
[ 4] 7.00-8.00 sec 11.2 MBytes 94.1 Mbits/sec 0 59.4 KBytes
[ 4] 8.00-9.00 sec 11.2 MBytes 94.1 Mbits/sec 0 59.4 KBytes
[ 4] 9.00-10.00 sec 11.2 MBytes 94.1 Mbits/sec 0 59.4 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 112 MBytes 94.2 Mbits/sec 0 sender
[ 4] 0.00-10.00 sec 112 MBytes 94.2 Mbits/sec receiver
iperf Done.
Code: Select all
[ 5] 3.00-4.00 sec 4.29 MBytes 36.0 Mbits/sec
[ 5] 4.00-5.00 sec 505 KBytes 4.14 Mbits/sec
[ 5] 5.00-6.00 sec 536 KBytes 4.39 Mbits/sec
[ 5] 6.00-7.00 sec 281 KBytes 2.31 Mbits/sec
[ 5] 7.00-8.00 sec 1.77 MBytes 14.8 Mbits/sec
EDIT: Is the other system that you are using for iperf using a wireless interface ? In that case your measurement may make sense.
The road to insanity is paved with static ip addresses
Re: Insanely slow network performance
I ran iperf3 -c pi3 on this mac which is connected via wireless, so that could be the source of the fluctuation. It's better than it was but it's still pretty crazy:
Code: Select all
4] local 192.168.0.10 port 55278 connected to 192.168.0.24 port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 218 KBytes 1.79 Mbits/sec
[ 4] 1.00-2.00 sec 86.3 KBytes 707 Kbits/sec
[ 4] 2.00-3.00 sec 67.9 KBytes 556 Kbits/sec
[ 4] 3.00-4.00 sec 0.00 Bytes 0.00 bits/sec
[ 4] 4.00-5.00 sec 563 KBytes 4.61 Mbits/sec
[ 4] 5.00-6.00 sec 6.02 MBytes 50.5 Mbits/sec
[ 4] 6.00-7.00 sec 8.17 MBytes 68.6 Mbits/sec
[ 4] 7.00-8.00 sec 7.85 MBytes 65.9 Mbits/sec
[ 4] 8.00-9.00 sec 1.12 MBytes 9.41 Mbits/sec
[ 4] 9.00-10.00 sec 223 KBytes 1.82 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 24.3 MBytes 20.4 Mbits/sec sender
[ 4] 0.00-10.00 sec 24.2 MBytes 20.3 Mbits/sec receiver
Re: Insanely slow network performance
https://www.amazon.co.uk/Unibody-Alumin ... +with+rj45PiGraham wrote:What adaptor are you using?jahboater wrote:Sorry, thats with a USB adapter. Your figure is about right for the built-in ethernet.
I was just showing what the Pi is actually capable of.
Its a bit pricey but Anker stuff is well made. No drivers are needed.
Not all USB ethernet adapters will give that sort of speed.