That's a GbE equipped H3 device running with Armbian defaults sharing a RAID-0 over two USB disks. Testing from a MacBook connected to an el cheapo GbE switch. Old boring BSP kernel is used, therefore no UASP possible, no special 'tuning'. Just defaults. If you would've done the same test with OS images from the board's manufacturer (Xunlong) results would be way lower (due to wrong cpufreq settings and also wrong THS / throttling settings which will lead to killed CPU cores and a pretty slow overall system running on only 1 or 2 CPU cores after load peaks).
Why do I emphasize on this? Since settings matter!
We (linux-sunxi community and Armbian team) developed better THS/throttling settings first for H3 devices and then for Pine64's A64 (already back in March). Based on the experiences we made with H3 the whole job was easy with A64 since both SoCs are pretty similar and even the BSP kernel drivers use the same wrong strategies (wrong for Linux use cases!). Unfortunately a lot of OS images have way too late or never been updated to make use of this (applies to situation with both H3 and A64 and is something I already tried to explain to you earlier. But you just ignored that ('a zillion words') instead of taking into account that settings of the OS image in use really matter if one wants to explore why network performance sucks)
Anyway: H3 is a bit slower than A64 and shows a single-threaded limitation in RX direction which is mostly responsible for the poor write test results (below 55 MB/s). And that's why I'm pretty confident that Pine64+ is able to get close to or even exceed 80 MB/s (with mainline kernel and appropriate storage and network settings). The boards I tested with that are now away are able to do this so lets hope TL Lim will send out new working ones (the math is really simple: adjust settings, measure network and storage individually, check bottlenecks and you know what to expect. We do this all the time at Armbian since this is one of the project goals: identify bottlenecks and come up with appropriate settings to push these little beasts to the envelope)
But as already written: just by using longsleep's original Xenial image one would already get approriate settings that work pretty well regarding both storage and network. That's also one of the reasons why we came up with official Armbian images that late (Pine64 and Pine64+ both being supported since May by our automated build system): since for those Pine64+ users that knew what they were doing there was no need for Armbian, longsleep's image worked fantastic from the very beginning (and there exists only one original OS image from him that's this here. None of the images available at http://wiki.pine64.org or https://www.pine64.pro is from him even if he's mentioned all the time. Those images and their users suffer from wrong settings and silly bugs like 'same MAC address')