It gets boring and while it's great that you don't do what you're usually doing (deleting/censoring stuff you don't get) you again spread only confusion.
I explained several times in detail why ondemand governor used on most 'featured' OS images is bad for performance. It's easy to test this out, you just have to get into details and do it. @pfreerick did exactly that, provided comparison numbers and even you were able to realize the difference between 9 MB/s and 29 MB/s? In his case he was bottlenecked by his USB 2.0 storage setup, with a better setup more is possible.
Then: I'm speaking here for experiences made by two far more broader communities: linux-sunxi and Armbian. Two years ago with devices based on old/boring dual core A20 SoC we were already able to get 44/72 MB/s in full NAS mode: http://linux-sunxi.org/Sunxi_devices_as_...erformance (but only with correct settings, baking a good OS image is not just throwing together u-boot, kernel and a rootfs found somewhere on the net but adjusting all settings accordingly. And BTW: that's the whole purpose of Armbian, the project started for exactly that reason)
A20 has a SATA write limitation and a GbE read limitation (A20 is dual-core ARMv7), A64 has balanced USB2.0 performance and no GbE limitation (and is quad-core and ARMv8 and contains new IP blocks for networking showing no limitation any more). A64 is just like H3 but more beefy and we tested H3 devices as NAS extensively. Everything is already known, if TL Lim sends out working boards I provide soon numbers. But hey, why? It gets so easy if you start to understand that Pine64 is based on an Allwinner SoC and that experiences with these devices do already exist: http://linux-sunxi.org
Most available OS images for Pine64+ show bad network behaviour/performance due to two single reasons:
The pine64.pro site was a joke from the beginning, collecting outdated OS images with wrong settings, empty FAQ and info pages for months, a so called bug tracker that does nothing and where people are able to report hardware issues as Linux kernel bugs (and no one cares about any of these 'reports' or assigns them to a developer or does anything useful with it, only confusion and the feeling for Pine64 noobies that 'something's happening there'). Unfortunately pine64.pro maintainer suffers from the same problem as you.
I explained several times in detail why ondemand governor used on most 'featured' OS images is bad for performance. It's easy to test this out, you just have to get into details and do it. @pfreerick did exactly that, provided comparison numbers and even you were able to realize the difference between 9 MB/s and 29 MB/s? In his case he was bottlenecked by his USB 2.0 storage setup, with a better setup more is possible.
Then: I'm speaking here for experiences made by two far more broader communities: linux-sunxi and Armbian. Two years ago with devices based on old/boring dual core A20 SoC we were already able to get 44/72 MB/s in full NAS mode: http://linux-sunxi.org/Sunxi_devices_as_...erformance (but only with correct settings, baking a good OS image is not just throwing together u-boot, kernel and a rootfs found somewhere on the net but adjusting all settings accordingly. And BTW: that's the whole purpose of Armbian, the project started for exactly that reason)
A20 has a SATA write limitation and a GbE read limitation (A20 is dual-core ARMv7), A64 has balanced USB2.0 performance and no GbE limitation (and is quad-core and ARMv8 and contains new IP blocks for networking showing no limitation any more). A64 is just like H3 but more beefy and we tested H3 devices as NAS extensively. Everything is already known, if TL Lim sends out working boards I provide soon numbers. But hey, why? It gets so easy if you start to understand that Pine64 is based on an Allwinner SoC and that experiences with these devices do already exist: http://linux-sunxi.org
Most available OS images for Pine64+ show bad network behaviour/performance due to two single reasons:
- wrong cpufreq governor as explained countless times, also how to fix this several times here
- silly mistakes like MAC address already set (that's just the result of people fiddling around and forgetting to adjust stuff before they release an image. And that's the reason why Armbian uses only script to create OS images from scratch: since such mistakes can not happen)
The pine64.pro site was a joke from the beginning, collecting outdated OS images with wrong settings, empty FAQ and info pages for months, a so called bug tracker that does nothing and where people are able to report hardware issues as Linux kernel bugs (and no one cares about any of these 'reports' or assigns them to a developer or does anything useful with it, only confusion and the feeling for Pine64 noobies that 'something's happening there'). Unfortunately pine64.pro maintainer suffers from the same problem as you.