[plug] SBC with 32gb ram

[Bill Kenworthy]

Overkill - not really. The calculations show I need at least 16G (its
currently using ~11G).  I was using an odroid-n2 with 4G ram - slowed to
a crawl when it hit swap and eventually crashed.  I moved the master to
a much more powerful intel server with 32mb and it has crashed once but
I was hammering it (graphs show it ran out of ram - need to check if the
OOM is disabled on that one).  Cheats like moving swap and the mfs
directories to a usb3 connected SSD helped (4-5 times faster than an SD
card), but eventually fell short.

I have 10 disks (~26Tb) spread across 5, soon to be 6 low power odroids
and an intel atom.  The problem came when I put two copies of 20+ years
email (millions of smallish files) on it and then reconfigured the mail
server to use one copy.   Yes, I know ...self inflicted! But it did work
for a few days! :)

There are some guide calculations on the moosefs website that match what
I am seeing for usage and support why I want at least 32G.  There are
still some shortcuts I could use (go back to putting the small files in
a qemu virtual disk) but that had its own issues.  I see some emails on
the moosefs website about masters with hundreds of G ram!

billK



On 22/11/19 10:53 am, Benjamin wrote:
> Hi Bill,
>
> 32GB of RAM is almost certainly overkill for a MooseFS master - what
> kind of files are you planning to store?
>
> ~ B
>
> On Fri, Nov 22, 2019 at 10:50 AM Bill Kenworthy <billk at iinet.net.au
> <mailto:billk at iinet.net.au>> wrote:
>
>     Hi,
>
>         I am looking for an SBC that can take 32gb ram, has a SATA (or
>     mSATA) connection and 1g networking - prefer ARM based and Linux
>     friendly. So far there is only the odroid-H2 (intel) that seems to
>     be at
>     a reasonable cost - but is there anything else out there that's
>     comparable?  Use is for a moosefs master server so I don't need a
>     super
>     fast processor, HDMI, media or fancy features.
>
>     BillK
>
>
>     _______________________________________________
>     PLUG discussion list: plug at plug.org.au <mailto:plug at plug.org.au>
>     http://lists.plug.org.au/mailman/listinfo/plug
>     Committee e-mail: committee at plug.org.au <mailto:committee at plug.org.au>
>     PLUG Membership: http://www.plug.org.au/membership
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.plug.org.au/pipermail/plug/attachments/20191122/971e6a3e/attachment.html>