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.]

Last edited by jtiscione on Mon Mar 20, 2017 2:02 am, edited 1 time in total.

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?

You have a problem in the network configuration, this can be hardware and/or software.
If you need help then please give more information, like what Pi, which OS release, network configuration, active interfaces, system activity.

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?

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.

Principal Software Engineer at Raspberry Pi (Trading) Ltd.
Contrary to popular belief, humorous signatures are allowed. Here's an example...
"My grief counseller just died, luckily, he was so good, I didn't care."

Ernst wrote:If you need help then please give more information, like what Pi, which OS release, network configuration, active interfaces, system activity.

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.

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.

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.

Ernst wrote:If you need help then please give more information, like what Pi, which OS release, network configuration, active interfaces, system activity.

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.

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.

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.

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.

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:

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.