Its not a biggy cuz I dont have any super high bitrate movies (yet), but it seems NFS networking performance is a little bit worse than on my Chromebox with openELEC/Kodi 15.2. I know the Vero has a 100Mbit LAN instead of 1Gb but still, it performs a tad worse than I thought it would. My “old” setup has no issues what so ever playing the jellyfish x264 100Mbit testfile without stuttering, where as the Vero starts to stutter at around 70-ish Mbit jellyfish testfile. Both the vero and my chromebox are connected to the exact same share, using haneWin NFS server, runninig on win10pro. Not sure what to make of that…I mean, if the chromebox can handle 100MBit stutterfree then the network is OK for 100Mbit, so the issue must come from how this “new” Kodi handles NFS compared to the old 15.2 Kodi, right? I know the recommendation is to use fstab, and thats completely new to me, but I will look in to it when I need to. But is there anyting besides fstab I can do to improve the NFS network performance?
100Mbit is theoretical maximum throughput. Real world is much closer to 85-ish. You are trying to compare apples and oranges against a gigabit Chromebox.
You should be ok for playback of real world content.
hmmm yeah I kinda suspected that. I know its not a fair comparisson, just asking cuz I needed to know wether there was any point in me trying to maximize the network speed or not. Saves me the hazzle of trying other nfs server settings and/or servers.
If 70Mbit jellyfish is ok, you should be fine.
iperf is the best way to test your network connection.
Well, you can also make a hardware upgrade to the Vero 4k and buy a USB-Gigabit LAN adapter (search in this forum what models users report to work). But as always with upgrades this costs some bucks, here in Germany around 10-15 EUR.
With an Anker adapter I can easily reach 35 MB/s when copying from a small Synology NAS to a HDD connected to the Vero 4k.
It is not necessary to play 4k videos but it creates some degree of comfort if you host your audio and video material on a local drive and often have to transfer huge amount of data by that.
Do a search on the forum for iperf3.
Done. So, its ok to discuss iperf, but not how to get it onto the device itself?
Oozee already provided the appropriate response.
Here is some info also on getting access to the command line of your 4k
Looks great 
Now I just have to figure out if I can improve the real world speed of my nfs share. If iperf3 meassures ~95MBit I should theoretically get stutter free playback of a 90MBit jellyfish, right? Or is there a bottleneck in using the normal nfs browser share in Kodi? Sorry for all nooby questions haha, but I am just learning all this stuff.
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-1.00 sec 11.0 MBytes 92.6 Mbits/sec
[ 5] 1.00-2.00 sec 11.3 MBytes 94.9 Mbits/sec
[ 5] 2.00-3.00 sec 11.3 MBytes 94.9 Mbits/sec
[ 5] 3.00-4.00 sec 11.3 MBytes 94.9 Mbits/sec
[ 5] 4.00-5.00 sec 11.3 MBytes 94.9 Mbits/sec
[ 5] 5.00-6.00 sec 11.3 MBytes 94.9 Mbits/sec
[ 5] 6.00-7.00 sec 11.3 MBytes 94.9 Mbits/sec
[ 5] 7.00-8.00 sec 11.3 MBytes 94.9 Mbits/sec
[ 5] 8.00-9.00 sec 11.3 MBytes 94.9 Mbits/sec
[ 5] 9.00-10.00 sec 11.3 MBytes 94.9 Mbits/sec
[ 5] 10.00-10.04 sec 418 KBytes 94.9 Mbits/sec
[ ID] Interval Transfer Bandwidth
[ 5] 0.00-10.04 sec 0.00 Bytes 0.00 bits/sec sender
[ 5] 0.00-10.04 sec 113 MBytes 94.7 Mbits/sec receiver
Mounting as an fstab local mount would be preferable and remove the possibility.
I got fstab up and running, and did some tests. It improved the throughput by about 15MBit. I am happy with that Thank you for all the help, much appreciated!
Excellent.