Also too low. And the htop screenshot confirms that IRQ affinity on this OS image needs some love. BTW: I was asking for iperf3 (not iperf) numbers for a reason: iperf3 also displays count of retransmits (nice to spot bad cables and/or switch ports).
My bad about mixing up iperf and iperf3, the windows machine had a iperf3 running, installed the wrong package on the Odroid-N2.
Lost/Total Datagrams are around 50% ... doesn't look good at all, probably the cables are not ok.
The switch is a Linksys LGS108 Gigabit Unmanaged Switch.
CPU usage is about the same as yesterday: +- 80% on CPU0
iperf3_100M.txt a little "less worse" I suppose...
I'll try with proper cables on the one I have at home.
Anyway: it's obvious that there is a lot missing wrt ideal settings with the NAS use case and ODROID N2 in mind. Maybe someone with interest in this device (definitely not me) looks into this and applies the relevant optimizations (that are well documented since years).
Would installing irqbalance help ?
I checked the affinity for the IRQ of eth0 and it is set to a 3F mask, so 6 cores.
for i in $(seq 0 300); do grep . /proc/irq/$i/smp_affinity /dev/null 2>/dev/null; done
All other IRQ's were the same except for IRQ 14 which is Meson TimerF.
Now this rings a bell as the driver for eth0 is listed as meson6-dwmac
dmesg |grep eth
[ 0.000000] psci: probing for conduit method from DT.
[ 0.832259] meson6-dwmac ff3f0000.ethernet: no reset control found
[ 0.838141] eth%d: PHY ID 001cc916 at 0 IRQ POLL (stmmac-0:00) active
[ 0.838148] eth%d: PHY ID 001cc916 at 7 IRQ POLL (stmmac-0:07)
[ 99.543109] eth0: device MAC address 00:1e:06:42:11:ec
[ 99.628584] meson6-dwmac ff3f0000.ethernet eth0: fail to init PTP.
[ 103.722826] meson6-dwmac ff3f0000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
Should I go ahead and put the same 3F affinity mask for IRQ 14 ?
Also the 840 EVO SSD is not playing well with the Odroid-N2, my first guess is that it doesn't get enough power from the board.
It takes ages to show up in the OMV4 disk list and performance over SAMBA was worse then the regular external USB3 disk I tested yesterday.
Then regarding UAS/UASP, the USB3 enclosure uses an ASM1051E SATA 6Gb/s bridge for which I checked the UAS compatibility: Blacklisted / UAS disabled
I'll pull it out and try with an USB3/sata dongle I have somewhere, maybe it uses another controller.
The 4.9.170+ kernel has UAS suport : CONFIG_USB_UAS flag is set.
Can't say about NFS yet, as shares would not show up on the Windows machine although the NFS components/services are installed.