Those cache drives are the low capacity consumer Optane products (which topped out at 120GB I think?). That drive is an enterprise/workstation drive with higher capacity (and a price to match). Optane is much faster than NAND, especially for random workloads and low queue depths, but it scales poorly in terms of density so it's poorly suited for mass storage sadly.
I had to learn that the word "cache" drive doesn't exist in the truenas world and especially truenas forum
But yeah, it's much easier to call it cache drive then try to explain what it ectually does 
Are you using it as an L2ARC? I was planning to use a spare 500GB SSD as a "cache" before I started learning the ins and outs of TrueNAS, and ended up skipping L2ARC entirely - it just didn't seem useful for my use case.I had to learn that the word "cache" drive doesn't exist in the truenas world and especially truenas forum
Funny thing is ixsystems (developer of truenas) also use the therm "write cache" in their description for their own systems ...
No not using as L2ARC. Only for SLOG/ZIL ("write cache"
).
Ah, you have a use for that? I decided against that seeing how my NAS doesn't get that much write activity. Or, the media drive does, but that isn't anywhere near performance sensitive, and rather intermittent still.No not using as L2ARC. Only for SLOG/ZIL ("write cache"
Yeah, adding more RAM instead of adding a SSD for L2ARC seams the better solutions. Adding a L2ARC device wil rob ARC (RAM) space to map the L2ARC which could also cost you performance than giving you a performance boost
I'm running Core, haven't even updated the system much (still on 12.0 U6.1), prioritizing keeping it running and working well. It's at 200 days of uptime right now, so I'm pretty happy. Still, lots of changes coming this summer - that storage upgrade I mentioned, plus finally getting my 2.5G NIC wired up. It's installed and activated (it's a Realtek NIC, so it needs a couple of tunables to activate the driver), but I'm waiting on having the NAS taken out of its cubby for actually giving it an IP as that necessitates deactivating the built-in NIC, and knowing my luck something will no doubt go wrong with that handoff
And having to get it out of there to install a GPU and get command line access to fix any issues will be ... well, not fun!
Same. While I generally love various DIY stuff - and am arguably doing more of it as of late - as I've grown older I've come to appreciate the distinctions between DIY for its own sake, DIY 'cause it gets me something I couldn't otherwise get/afford, and DIY because it gets me something I want/need (but could just buy). And the latter is looking increasingly unattractive. With the risks and hassle involved with DIY, if you actually need the end product to work, having the time to troubleshoot and fix things on a DIY project is an immense privilege that my life mostly just doesn't afford me. DIY stuff is fun and rewarding on its own, and removing the stress of "damn, I actually need this to work" improves the experience; DIY that gets me something I couldn't otherwise get is similar, and lowers the stakes as failure typically isn't a big deal (while success might be very nice); DIY to make something that I actually need to work, that's essentially taking on a second job/unsupervised apprenticeship as a maintenance technician for whatever that thing is. These obviously blend into each other (the existence of the DIY 3D printer market is precisely because most people couldn't initially afford to buy one, after all), but learning to identify which project idea fits into which category for me is proving to be a very valuable life skill.
Your account should lapse off the old subscription today (or yesterday NZ time
). I can force it early, but you did pay for that time
It's done... Hopefully back on the sub train.Your account should lapse off the old subscription today (or yesterday NZ time
