Building a NAS and compute node for work
3 minutes ago, bogate said:Users around 10, i am guessing max 500GB traffic on the busiest day.
Work being a business. I dont know if we have supermicro in germany but i will look into it. Thanks your recommending about splitting the NAS and the compute node. That has been a big discussion point.
Regarding amd epyc, are they not much more expensive and slower than the desktop CPUs? I think that would be overkill for the NAS and for the price of an amd epyc (3500$ for a 32 core) we could just get 2 systems with 7950X. For simulations we would prefer two fast 16 core system vs one slow 32 core system. We do have access to a cluster for high core count work.
for the NAS i'd honestly just get a small off the shelf server (for reliability purposes) or a rackmount synology.
as for epyc for the compute side, they're not *that* insane once you price out the entire thing, especially if you add in that the epyc motherboards may include stuff like 10gig lan and ipmi.
but the beauty of epyc is the amount of expandability you have access to. you could literally have a douzen M.2 SSD's in there as your fast storage, and still have the lanes for multiple GPU's if you feel so inclined. i guess it does depend on how much reliability matters, and how much GPU acceleration you can do.
if reliability doesnt really matter for the compute node (reliability in the meaning that issues do happen occasionally, not that it's gonna set on fire in a week) sure thing get a bunch of enthousiast CPU's and overclock the living heck out of them.
that's another good reason to split NAS and compute too, now i think of it: NAS is 100% about reliability. for a compute node you may as well fly closer to the sun if you can get 10% more performance with 2% more downtime.

Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now