I'm kind of regretting not buying some of those used 3.84TB sata SSDs when they were regularly $160.
Welcome to the ClubI'm kind of regretting not buying some of those used 3.84TB sata SSDs when they were regularly $160.
I got a legit drive from the listing. $878.99 OBO now.There's a $888 1.6TB p5800x on ebay from what appears to be a reputable Chinese seller.
Did his account get hacked or is this a scam? This is the optane holy grail at 50% off. Anyone brave enough to buy one?
Also doesn't help that he has 100 of it apparently.

If I hadn't just gotten a good deal on a pair of brand new 1.5TB p4800x drives this would be irresistible.
The latency difference is enough to make regular tasks noticably faster, kernel builds and runningOut 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?
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.)Faster than what?The latency difference is enough to make regular tasks noticably faster, kernel builds and runningfind, that sort of thing,
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.Faster than what?
Back from my Gentoo Days I would always build onI 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.
tmpfs (RAM).I often rebuild after minor changes so persisting all the intermediate build files speeds things up, alsoI'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.
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.I often rebuild after minor changes so persisting all the intermediate build files speeds things up, alsotmpfsisn't always that fast, I run containers with tmpfs volumes forbazelbuilds 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.
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.NVMe faster than RAM?
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 oneAlso that should only be the Case if you are running out of RAM and are rebooting the Server often.
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.)Fair Pointplus 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.
It depends on the Host.I don't know how much RAM you have
128GB RAM for a Kernel Buildbut 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 onemakejob 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.)
That was me who bought 2 drives out of 3 available. I don't need more, won't snipe it again.Gone with the wind :-O