Building an SBC NanoPi SATA hat based NAS

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • esbeeb wrote:

      Writing many tiny files, like a whole bunch of small ebooks, over GbE (this use case is the one most important to me) to an RK3399-based SBC, will probably yield no more than about 40MB/sec
      As it's the case with any other GbE equipped device, be it x86 or ARM, right?

      A bunch of small files will always end up being transferred way slower than some huge files, there's nothing one should be surprised about. It's about knowing the individual bottlenecks between the client's and the server's disks and understanding how they 'interact'.
    • esbeeb wrote:

      Did you send a few larger files over rsync, or a bunch of tiny files?
      He sent one file (since received 35 bytes). But in his case wireless is the bottleneck anyway and due to higher latency sending a bunch of really small files wirelessly will take more time than over an Ethernet connection with lower latency (bandwidth and latency are two different things but always interact).
    • OK, I tried uploading 2GB of ebooks (2029 files in 756 folders) to my Nano Pi Neo2, just to compare.

      The upload happened through all-GbE, and I tried two different GbE dongles on my laptop (An Anker AH212, and a TP-Link UE300).

      I uploaded using rsync, into a SATA drive connected to a USB port on the NanoPi (the SATA drive was in a SATA enclosure, with a JMS578 chip). Both dongles had almost the exact same speed: 19.3MB/sec for the TP-Link, and 19.1 MB/sec for the Anker.
    • esbeeb wrote:

      two different GbE dongles on my laptop ... I uploaded using rsync
      What a great test given that I already tried to explain the latency stuff (USB --> high latency) and also this in the very same thread here:

      tkaiser wrote:

      With rsync and scp you're likely to be CPU bound since encryption might be involved now and then single-threaded CPU performance starts to matter depending on which cipher got negotiated between machines
      So the next time you retest you might want to fire up htop on your SBC and most probably see one CPU core being at 100% all the time?
    • I just got my M4 and SATA hat as well. I bought a Meanwell LRS-100-12 and plan to power the M4 over the 4 pin connector and shove everything into one of these.
      Maybe I'll add some sort of case around it (3D printed or laser cut acrylic or something similar). I can add a fan in the front if needed.
      I have 2 HDDs and I'll probably add a SSD, so power shouldn't be an issue.

      EDIT: Too bad they didn't solder any pins next to the power button on the hat, that would have made it easier to connect a separate power button... I guess I'll have to solder it myself.
    • frauhottelmann wrote:

      I just got my M4 and SATA hat as well. I bought a Meanwell LRS-100-12 and plan to power the M4 over the 4 pin connector and shove everything into one of these.
      If time permits please open up a new thread in "My NAS build" subforum with pictures then :)

      frauhottelmann wrote:

      Maybe I'll add some sort of case around it (3D printed or laser cut acrylic or something similar)
      My main concern with spinning rust is vibrations so I clearly would prefer vibration free montage (inside a cabinet or similar) than a slightly unstable enclosure helping with vibrations.
    • Users Online 1

      1 Guest