 Tom here from learn systems and how much memory do you need for a ZFS and wait? I know it must be you need for each terabyte of storage You need at least so many gigabytes of memory. There's some formula, right? It's a little fuzzier than that and that answer has been at the top of Google search results I think too long because that's not the most accurate way to do this What we're going to cover in this video is one that you don't need that much memory for ZFS But if you do use lots of memory, you're gonna get better performance than the ZFS I've got a couple of videos where I dive into the why which is of course cashing the more memory you throw in there The better the arch cash will be therefore the better performance that videos link down below right demystify Hopefully the ways that the cash system works kind of a side note is what about ECC? Isn't that a requirement for ZFS isn't my data at risk and I'm putting all of this data You know in in the hands of one bit flip and destroying all of it. That's not true either I've got a video talking about ZFS being a cow copy on right file system And don't worry the data integrity is fine even if you're not using ECC. Is it better to use ECC? That's a general yes because from a computing standpoint and having error correcting memory is a good thing But it's not a required thing in order to do this So I wanted to clear those up right away now Let's dive into and we're gonna talk specifically about true NAS But this applies to GF ZFS in general when you're setting this up for how much memory you need for your ZFS system Okay, we're gonna start at the low end. This is my low end Intel Atom system This is what I call my purple NAS because I had a handful of Western digital purple drives that I put in here Four of them to be specific. Let's actually look at the storage real quick here and we'll see that I'm only using four terabytes out of 22 terabytes that are still free So just under 30 terabytes of storage on this. This just keeps backup copies of things. So performance is not an issue They're backups of my videos. So I'm not worried about how long it'll take to get them back But if my main NAS fails, hey got a second copy But I restarted it just a little while ago because I want to just clear it from copies I've done when backing up and putting files on it to show you that with eight gigs of memory It's still not even using I have five point five gigs free now If I start copying files back and forth it will use some memory and if we go and look at these services I'm using in it to get the data back and forth such as our sync. I have an our sync job that talks to it I've got SMB if I need to copy some files to it SSH, which is part of facilitating ZFS send So my main video editing churnass copies all the data back over to this one on a very regular basis Because hey, why not it doesn't take much. It's only doing differential copies So this job actually runs frequently, but it just doesn't take a lot of performance and as you note I have quite a bit of Terabytes of storage that don't match up with the amount of memory and the system is completely functional and works well No, other than being slow, but it's slow because that Intel atom more than anything else Combined with some older spinning rust drives. Now, let's talk about my video editing system When you get to churnass scale versus core, there's some differences specifically cuz scales built on Linux by default It does not use all the memory. It will only use about half of it So we do have 64 gigs of RAM in my video editing system because I could probably even use more all the videos and actually This is why it's under load. My videos as a record them right directly to this system They're getting cached. This makes it really fast when I got to pull those videos into the editing software So that comes right out of cash and because I've modified the parameter I'll leave some notes in description below to tell it to use 50 gigs of cash. It's using 50 gigs of ZFS cash There's always files moving back and forth in my video editing. This gets me much better performance now Even though this is SSD volumes They won't quite peak out that 10 gig Nick But they'll come way closer to picking up the 10 gig Nick when you're pulling things right out of memory So this is where having more memory does help quite a bit Now let's move over to one of our production core systems at my office and this system has a 128 gigs of memory It's pretty much all used all the time for ZFS caching There's some services going on because we run several s3 Targets for different backups that land here and this system benefits from having a lot of memory It would benefit more with more memory. Well, we still got 5.2 gigs for you So maybe not that much more but this is using all the cash for serving up the Virtualization targets that talk to it or some of the backup from restores when I do backup restores They pull from this when I have my virtual machines running NFS This is the storage target for them and because NFS and VMs are going to be a lot of frequent rights or frequent reads more Specifically for database stuff that's getting pulled It just gets all in the cash and serves this up very fast now This does have 27 spinning rust drives in it But the cash will supplement and really make those frequently called files Which is a typical use case serve up extremely fast combined with a fast processor to get the data back and forth there And this system actually performs and has the IOPS performance similar to an SSD array It's not going to be a one-to-one comparison It's going to vary by workload But this is an example of where having a lot of memory helps a lot when we have clients that have large Virtualization systems are using TrueNAS core as a large target for those we load up as much memory as Reasonable to their budget budget is usually a constraint at some point for how much you buy But loading a system up a 512 For a TrueNAS system is not uncommon because it will give you really good read performance for all those Frequently accessed files or in the case of like a system running 80 or 100 virtual machines across several Different hypervisors and pulling the data off here or in the case of video editing We have a lot of clients in that space that are more than just a single editor like myself If you have a team of editors pulling files pulling them out of memory is always going to be faster than pulling them off the drives As I said in the video I use TrueNAS as an example But it does apply to really any system using ZFS You don't have to have a lot of memory But the memory will greatly help the performance of whatever system is running ZFS So it's allowed to use more memory means better caching that caching video I dive deep into the details of that ZFS is really smart and intelligent It'll take all the memory and all those files back and forth and commit them there So any service requesting them can get at them faster But if it doesn't have them you're just going to pull off the drives and work at whatever rate that operates at depending on your system configuration Let me know what your thoughts are in the comments down below or to engage me further on this header my forum for a More in-depth discussion. Thanks