Enterprise SSD "small deals"

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

ca3y6

Well-Known Member
Apr 3, 2021
928
943
93
Out of curiosity, what do you guys use it for? You can get a similar endurance by buying a 10 times larger drive for the same price. I know these things have a low latency, but what can possibly require such a low latency in a homelab context?
 

nexox

Well-Known Member
May 3, 2023
2,070
1,041
113
Out of curiosity, what do you guys use it for? You can get a similar endurance by buying a 10 times larger drive for the same price. I know these things have a low latency, but what can possibly require such a low latency in a homelab context?
The latency difference is enough to make regular tasks noticably faster, kernel builds and running find, that sort of thing, and lately prices are such that I would be looking at QLC SSDs to get 5x the capacity at the same cost, I haven't seen anything with comparable write life per dollar in the last 6-8 months. (edit: except maybe those drives that keep popping up in this thread, but they're never in stock when I look. edit 2: even those are 28PBW vs the 164PBW for my p4800x drives.)
 

nexox

Well-Known Member
May 3, 2023
2,070
1,041
113
Faster than what?
I admittedly don't have any huge NVMe drives to compare, but my sx350s roughly match the p4800x specs in most aspects (and where they fall short of the Optane drives they're well ahead of TLC,) yet have 10x the read latency, they're noticably slower for any workload that hits lots of small files or a bunch of filesystem metadata.
 
  • Like
Reactions: ca3y6

luckylinux

Well-Known Member
Mar 18, 2012
1,716
578
113
I admittedly don't have any huge NVMe drives to compare, but my sx350s roughly match the p4800x specs in most aspects (and where they fall short of the Optane drives they're well ahead of TLC,) yet have 10x the read latency, they're noticably slower for any workload that hits lots of small files or a bunch of filesystem metadata.
Back from my Gentoo Days I would always build on tmpfs (RAM).

I'm not sure why you would use a (comparatively) much slower NVMe Drive. Just build in RAM, create an Archive, then move to persistent Storage.

I will probably have to look into the same with some CI Server (Forgejo Runner). Right now I'm just doing my "Default" Podman Setup.
 

nexox

Well-Known Member
May 3, 2023
2,070
1,041
113
I'm not sure why you would use a (comparatively) much slower NVMe Drive. Just build in RAM, create an Archive, then move to persistent Storage.
I often rebuild after minor changes so persisting all the intermediate build files speeds things up, also tmpfs isn't always that fast, I run containers with tmpfs volumes for bazel builds with a network cache (so I don't need to persist files locally) and just cleaning up a 64GB tmpfs volume can take 20-30 seconds - if I had Optane drives at work I would not be surprised if they built faster over all.
 
  • Wow
Reactions: luckylinux

luckylinux

Well-Known Member
Mar 18, 2012
1,716
578
113
I often rebuild after minor changes so persisting all the intermediate build files speeds things up, also tmpfs isn't always that fast, I run containers with tmpfs volumes for bazel builds with a network cache (so I don't need to persist files locally) and just cleaning up a 64GB tmpfs volume can take 20-30 seconds - if I had Optane drives at work I would not be surprised if they built faster over all.
NVMe faster than RAM ? Weird. Also that should only be the Case if you are running out of RAM and are rebooting the Server often.
 

nexox

Well-Known Member
May 3, 2023
2,070
1,041
113
NVMe faster than RAM?
RAM is faster, the tmpfs implementation just has some slow parts, plus you're still copying the files from NVMe to tmpfs before you can do anything and then at least some files back again when you're done.

Also that should only be the Case if you are running out of RAM and are rebooting the Server often.
I don't know how much RAM you have but a kernel build will occasionally hit my cgroup limit of 128GB on its own if there are a lot of options enabled and I run one make job per.core, that doesn't leave a ton of memory to waste on long term storage of intermediate build artifacts (and at work it's all ephemeral instances anyway.)
 

luckylinux

Well-Known Member
Mar 18, 2012
1,716
578
113
plus you're still copying the files from NVMe to tmpfs before you can do anything and then at least some files back again when you're done.
Fair Point :). Or to/from SATA for me. Just installing Kernel Headers on Linux takes forever for me :p.

I just installed Proxmox VE on the Hyve Servers I bought a while ago (on an NVMe Mirror out of 800GB / 960GB / 1.2TB / 3.2TB / 3.84TB, depending on what I had available) and now I'm basically out of NVMe, except 5-6 x consumer Crucial P5 Plus 2TB. The SAN Server will basically be only SAS 12G / SATA 6G plus maybe 3 x (6.4TB PCIe, though that is actually 2 x 3.2TB). No more NVMe available. Prices are currently crazy and Wallet is empty :(.

I don't know how much RAM you have
It depends on the Host.

32GB on some Supermicro X10SLL-F/X10SLM-F Motherboards

64GB on Supermicro X11SSM-F/X11SSL-F / AMD Ryzen 3600/3700X Boards.

All the Way up to 512GB DDR4 on some AMD EPYC 7642 Systems (Hyve).

To stress test a CPU and check Thermals I typically just build the Linux Kernel, with default Options.

I never had a Problem building the Linux Kernel (6.12.23) on 16GB tmpfs on one of the smallest Systems.

but a kernel build will occasionally hit my cgroup limit of 128GB on its own if there are a lot of options enabled and I run one make job per.core, that doesn't leave a ton of memory to waste on long term storage of intermediate build artifacts (and at work it's all ephemeral instances anyway.)
128GB RAM for a Kernel Build :oops: ? Holy smokes !