3 ms·
> 2. those disk support sata 3 @ 6.0 gbps, but the network interface on the odroid (as well as most other SBCs) is a 1gbps. not surprisingly, the graph for thro
by trojan295 5y ago
> 2. those disk support sata 3 @ 6.0 gbps, but the network interface on the odroid (as well as most other SBCs) is a 1gbps. not surprisingly, the graph for throughput kinda reflects that: the best performance for network-based sequential read (jiva) tops at about 1/6 of local physical volum device. iops for sequential reads are similar.
Jiva for sequential reads was 20MB/s, so the 1gbps network port wasn't saturated at that point.
- znpy 5y agoIndeed, indeed. What I wanted to say is that even if Jiva had no performance penalty, it would only deliver at most 125 out of the 220 MBps that the drive is supposed to be capable of sustaining.
- trojan295 5y agoOh yeah, I agree here. That's why I think it would be nice to try the Mayastor engine, which, based on some benchmarks, provides much better performance. I'm curious, if still the OpenEBS would be the bottleneck, or maybe I hit the SBC limitations. Unfortunately, I'm not sure if they are planning official ARM64 support...