The Western Digital WD Black SN850 Review: A Fast PCIe 4.0 SSD
anandtech.com
anandtech.com
I've started to upgrade parts of my network to 10Gbps, and it was surprisingly affordable. My NAS and server now have a dedicated 10GB Gbps link between them (the NAS also has 4 1Gbps connections to my primary network), and it only cost about £50. Obviously it still could be a bottleneck, but it's a decent step in the right direction.
For video editing I can use the SSDs on the workstation, though I can also saturate the 10GbE connection to an iSCSI target on a Synology full of hard disks in RAID 10.
Want to provision a new virtual machine? I have some 1L form factor computers (Some 175x175x35mm HPs with 8-core Ryzen 7 PRO APUs that sip 12-15W at idle) in an XCP-NG cluster. Build an image and provision it quickly. I'm a bit limited here as USB 3 NICs tend to cap out at 3.5Gbps because the top of the controller's block diagram is a 3.2 Gen 1, but when USB Type-C Gen 2 NICs hit they'll rip along at around 7-8Gbps, pulling large built images down from the Synology and writing it to their SSDs (980 Pros) in well under 10 seconds.
Scary stuff though is the virtualized Spark cluster running on my workstation. Four Intel D7-P5510s in RAID10. With ~25GB/sec of sequential reads you're not held up by storage anymore. Just the network when you want to write out results, and any suboptimal code to ensure you don't starve the CPU cores because you're not ripping through memory fast enough.
The fast new reality is great. Join in. :)
Regular 1GbE is sooo low now.
Not got the switch yet, just running point to point. Using a different IP range so I'm sure I'm hitting that 10G goodness.
[1]: https://www.fs.com
I've got a fairly extensive home lab network but I've been "stuck" at 1 GbE for several years now, mostly because I couldn't justify the cost of upgrading to 10 GbE. See, I'd need a switch with a minimum of five 10 GbE ports -- just for the FreeNAS box, my workstation, and three of the VMware nodes; if I were gonna make the jump to 10 GbE, I'd want to upgrade those machines, at the least.
A couple years ago I bought a pair of cheap, old Mellanox 10 GbE cards and a short direct-attach cable (DAC) to directly connect the FreeNAS machine and the "giant" VMware box (which has roughly the same "horsepower" of three of the others combined!) that I ran most things on. For the most part, everything else has a single 1 GbE link, except for my workstation (2 x 1 GbE) and the other VMware servers (4 x 1 GbE).
Anyways, I recently started thinking about upgrading and/or replacing some things. While doing my research, I came across recommendations for some specific (enterprise) network gear that -- having been mostly a Cisco / Juniper guy for the last 15 years or so -- I wouldn't have normally considered (and, no, MikroTik is NOT an option, for several reasons). I also learned a few "interesting" pieces of information, like how to magically turn some specific (relatively cheap) 10 GbE NICs into (not so cheap!) 40 GbE NICs just by flashing different firmware on them.
I also ended up getting a set of server rails and a small box full of dual-port 10 GbE NICs "free" when I went to buy the set of rails from a guy off Craigslist. They were Broadcom NICs but they'll work just fine in the other VMware servers!
So, by the time I'm done with everything (I'm also in the process of building a new room in the basement just for the lab), my FreeNAS box and workstation will both be connected at 40 GbE and the half-dozen or so other servers will all be connected at 10 GbE (although, to be honest, I will very likely end up connecting the second 10 GbE ports on them all, too; I'll have enough 10 GbE ports left on the switch.).
Before any asks, I'm not sure how much I've spent on the upgrade (and I'm halfway afraid to total it all up, honestly!). I've almost certainly spent more than I had originally planned when first starting to think about doing all of this but: 1) the additional cost to go to 40 GbE on the storage box and my workstation was really that much more so it was easy to justify, 2) once I'm all done with everything, I'm gonna get rid of the "giant" VMware box and, quite likely, a few of the others -- and maybe even some of the other things I've forgotten I have and/or don't use anymore; that should make the total overall cost fairly neglible, and 3) I've got 40 gigabit at my house!
Of course, at this point, the storage server won't be able to come close to saturating the 40 GbE link... which means I'll need to add more, faster storage... rinse and repeat, it never ends! Just say no to home labs, kids!
(I don't know much about this space and feature-wise they seem pretty useful for me.)
If 3200 is your RAM's stock speed, you can probably run it at least 10% faster using "DRAM Calculator for Ryzen".
I have a Ryzen 2600 with an Asus B450-Plus motherboard, and recently tried to upgrade to 3200MHz DDR4 (from 2666MHz) - I used the DRAM calculator (which is quite confusing TBH), but no matter I tried, it wouldn't even boot at anything higher than 2666MHz @CL16. A bit disappointing, but I still ended up with more RAM overall, so not a disaster.
The many-in-one diagrams let you switch between different diagrams by clicking on a label. However, the technique that has been used is inferior, making it not obvious (difficult to find), a bit more difficult for touch input, and impossible for users of accessibility tools or those not executing JavaScript.
Here’s roughly how it’s implemented:
<td onclick="document.getElementById('destroyer_bar').src = 'http://images.anandtech.com/graphs/graph16505/destroyer-power.png'">…</td>
The most important problem with this is that the table cell can be clicked on, but can’t be focused. You should roughly never have a click handler on a non-focusable element, focusable meaning elements like <a href>, <button>, <details><summary> or something with a tabindex="0" attribute. (But note that just adding tabindex="0" would not be sufficient, because onclick wouldn’t be triggered on pressing the Enter key. On links and buttons it does, because onclick is a misnomer for them, firing on activation rather than mouse click.)This would be far better markup, probably paired with style adjustments to shift the table cell padding to the anchor, and making that anchor `display: block`:
<td><a target="_blank" href="http://images.anandtech.com/graphs/graph16505/destroyer-power.png" onclick="document.getElementById('destroyer_bar').src = this.href; return false">…</a></td>
That way, (a) the link works without JavaScript, opening the requested diagram in a new window; (b) with JavaScript, it behaves as previously, except that it’s now focusable, so users of screen readers can interact with it; (c) as a link, it’s more discoverable (e.g. hover and it’s obviously interactive, where with the current one, I was just guessing based on the framing that maybe it was interactive despite all the signs telling me it was just text); (d) as a link, tapping on a touch screen will work more reliably (the browser will be more inclined to interpret a tap that moved slightly as a click rather than panning).One other thing I just noted: them http: URLs should be https:.
That's really unfortunate, because your technical content is among the, if not the very best in the business. But clearly there hasn't been much investment into the presentation side over the last years.
There's this German hardware review site [1] that has an almost embarrassingly good system for graphs like this, I'm sure you are aware of it. Would be really amazing if we could somehow get that level of presentation for your content!
[1] https://www.computerbase.de/2020-09/samsung-980-pro-ssd-test...
> you need to make sure you're using a heatsink.
[0] https://www.youtube.com/watch?v=M059dQg3d5c&t=569s
There's a section called "Fire! (Not really)" which demonstrates the 100°C temperatures "within minutes of testing".
I plan to build a second computer for this work, but this time with PCIe v4 SSDs; this is to expand capacity, not because I think it will have less problems or be faster overall, a throttled disk is painfully slow.
The solution is to get an enterprise drive, because they don't use SLC write caching and can usually sustain somewhat better write speeds as a result (plus, they're generally rated for more write endurance).
Heatsinks like the big chunk of metal in that video are only really good for delaying thermal throttling by adding extra thermal mass. The drive will still hit 100C and still throttle if you push it hard enough. Only airflow will remove heat from the drive.
If someone has workloads that are so consistently intense that throttling is causing an impact, they probably shouldn't be using consumer drives anyway. Server grade drives are designed for sustained workloads.
When your drive can sustain 7GB/sec read speeds and 5GB/sec write speeds, you can read an entire 1TB drive in about 2.5 minutes and write the entire drive in 3.5 minutes. Throttling will kick in after a minute or two, but the bigger problem is that if you're doing this consistently you're going to exhaust the drive's 600TBW write endurance very quickly.
In theory, if throttling wasn't an issue you could consume the entire drive's write endurance in a matter of days. If you're doing that level of writing, it's time to upgrade to more appropriate hardware.
What is the right hardware for that kind of workload?
Sufficient airflow across the motherboard is also important, of course.
https://www.ebay.com/itm/20Pc-ST036Y-12-12-3MM-Aluminum-Heat...
https://www.ebay.com/itm/12pcs-14x14x6mm-Small-Anodized-Heat...
https://www.ebay.com/itm/12pcs-Small-Aluminum-Heatsink-Cooli...
In addition to non-adhesive thermal paste, everyone should have a small tube of heatsink adhesive for building modern x86-64 desktop PCs from parts.
Based on known program/erase cycle limits for the NAND they're using, SSD manufacturers can make pretty accurate projections for how long (in TB written) the drive as a whole can survive, accounting for how that drive's controller manages the flash and what kind of write amplification can be expected from the intended workloads.
The most significant limitation where manufacturers have to go out on a limb with their projections pertains to the standard requirement that a consumer SSD needs to be able to retain its data in a read-only state for a year after reaching the end of its rated write endurance. NAND manufacturers can very quickly bring flash to that level of wear, but they can't wait a year to measure retention characteristics before shipping. So they make projections based on high-temperature accelerated testing.
Increasing over-provisioning, as I suggested in another comment, allows garbage collection to run less frequently and reduces the write amplification factor. Sequential large writes will also reduce write amplification factor. Rewriting blocks that are only in DRAM cache or dynamic SLC will also reduce wear.
Most applications that run on AWS and GCP don’t really need that premium Xeon/EPYC CPUs, enterprise-grade storage that is 10X the cost of consumer grade drives. Of course, those that do may justify the premium cost. But, the rest that just runs a few web servers behind a load balancer and non-critical services could use stuff on the cheap...
Say cheaper digitalocean built upon bare metal consumer grade hardware - Ryzen CPU, consumer grade memory, this Local NVMe storage, and the onboard network card... may be I am crazy to think that’s enough.
Heck such hardware may even perform better than several enterprise grade VMs provided by cloud providers.
I think a lot of Devs have had the surprise that their laptop has higher single core performance than a server.
I don't know to what extent but space is certainly a premium. For a unit of rack space you want to maximise the cores and memory.
With a server grade multi socket CPU, you're also likely to pair it with at least 512gb of ram.
Consumer CPUs have a much lower limit. Though Threadripper is a bit higher.
There's also the availability side of things. How many CPUs can you get to populate your datacenter?
Will it be easy to order 500 consumer CPUs if you're not a retailer? Intel/AMD do want to steer their enterprise customers to higher volume parts.
I think backblaze did just that with hard drives when they were starting out
Forget consumer grade: even normal Dell/HP/Supermicro stuff is a PITA to run at datacenter scale. Most major cloud providers roll their own machines for a reason.
I'm guessing any hardware savings would be evaporated by increased labor, power, and footprint costs, likely making you more expensive than other providers.
not if you know what you are doing.
Yes it is a pain. All these incumbent vendors have atrocious tools, management interfaces, and dealing with firmware is basically the same as 1990.
Major cloud providers got off “commodity enterprise” over a decade ago. There’s a reason for that.... the stuff is just bad.
> consumer grade compute
Non-ECC compute is a no go from start. You won't believe how computers make mistakes when they're driven to their limits. Even with good cooling, frying RAM, CPUs and ethernet gear is ordinary events.
> local storage
Consumer grade HDDs are slow. SAS is not consumer grade. Consumer grade SSDs cannot handle the write cycles. The ones which can handle neither cheap nor consumer grade.
> internal networking
Gigabit ethernet is cheap but, is not fast enough anymore. 10Gig+, Infiniband and other stuff needs reliable high bandwidth PCIe, which is not in abdunance in consumer grade hardware.
You need more lanes, then we come to next point.
> Most applications that run on AWS and GCP don’t really need that premium Xeon/EPYC CPUs
Server CPUs are not about processing power all the time. Reliability, PCIe lanes, expansion and advanced virtualization which allows that high performance network to be connected in abundance and shared between VMs without performance penalties. So you can scale the number of jobs running on less hardware in smaller spaces.
> enterprise-grade storage that is 10X the cost of consumer grade drives.
Again, it's not about performance but about reliability at least half the time. Performance is required to be able to scale, not for independent jobs.
Many modern amd offerings support ecc memory, but I can't comment on intel.
> Consumer grade HDDs are slow.
Meanwhile cloud provider hdd storage is slower than usb2. I have a 32 core machine deployed in azure right now, and the hdd that was deployed with it has a max read speed of 10MB/s. Getting a medium performing SSD seems to cost in the realm of $250/month just for the storage, before computer costs.
For many uses, users don't care about true reliability. I don't care if my CI agent has data loss, I'd _much_ much rather it ran on consumer grade hardware at speed and failed 2-3% of the time than what I've got now (as long as I have the choice. I want my build servers to run on fast unreliable hardware, for example)
Agreed re: pcie though!
That's because they're not bare hard drives directly connected to the server, they're a virtual hard drive over SAN.
It's said before, but I want to expand a little bit. You're getting 10MB/sec because your volume is running as a virtual disk on a SAN system which runs on 100s on disks which can read 15+ GB/sec, but serving to 1000 servers at the same time.
If you had local storage, you'd have the same speed because your storage backbone would have the same throughput/consumer ratio.
You want faster drives or higher throughput/consumer ratio? You'd need faster RAID cards with faster drives and more PCIe lanes.
Guess what? This is enterprise hardware again :)
> For many uses, users don't care about true reliability.
Reliability does not always concern with noisy problems (data loss, crash, file loss, etc.). The biggest problem is silent corruption. A wrongly compiled, somewhat buggy binary. A slightly wrongly trained model. A wrong outcome from a computation or simulation.
Lost files are not a problem. Wrong outcomes looking right is.
When you squeeze 50 low-pressure VMs to a single VM, they become a one high-pressure load.
Hence, you need enterprise level hardware to be able to provide these low-cost, eh performance VMs to masses.
Consumer boards for Ryzen CPUs support ECC RAM these days. So, it's not as bad as you think. Is it as reliable as a server board? probably not.. But, I'm not building for or paying for that reliability either - fitness for purpose.
I think your comment on storage missed the whole point. The article was about a PCIe 4.0 SSD that I wished to use in servers. They are every bit as fast as the enterprise grade NVMe drives. The differentiation is typically power loss protection. At consumer grade service levels, I don't care, I go cheap, but insane value. Again, fitness for purpose.
Networking. I can find a Asus board for Ryzen CPUs with onboard 10G NICs.
Sure, server CPUs have more lanes etc and are designed for maximum load sharing across workloads. My quest is the opposite. Give me small, cheap, and insane value servers instead of VMs that are running dog slow in beauty servers used by a hundred others.
Hello fellow HPC admin. I'm reporting in from another HPC center. Nice to chat with you. :)
> The differentiation is typically power loss protection. At consumer grade service levels, I don't care, I go cheap, but insane value. Again, fitness for purpose.
I don't think power loss protection is an enterprise level feature anymore. My Samsung 860 Pro has S.M.A.R.T attribute 235, which reads "POR_Recovery_Count". AFAIK, this attribute counts the times drive has lost power unexpectedly and had to do some housekeeping to recover itself.
AFAICS, the drive has 600x write endurance (1 TB version has 600TBW and it's linear with capacity), and if this thing is used in a VM server, it'd die in months. This is where enterprise drives matter. We have some SSDs designated as write caches for high performance ZFS appliances, and they didn't blink an eye to all this hammering.
> My quest is the opposite. Give me small, cheap, and insane value servers instead of VMs that are running dog slow in beauty servers used by a hundred others.
I understand, but as an HPC admin, you know that space is always at a premium. Having a Ryzen with 24GB ECC RAM and this drive on a non-system-room form factor is a waste of space and cooling capacity, and in today's integrated system room it's very hard to manage without IPMI.
So, at the end of the day, no cloud provider will touch this with a 10 feet pole. Even if they roll similar platform on a custom open-compute chassis, they'd opt for a more powerful system because it can a) can fill more roles, b) will be more efficient in terms of performance/watt since they can keep it more uniformly loaded and utilize it more.
From my point of view, this is the sad reality unfortunately.
You are paying more but mainly when the capabilities are better. Example for SSD: Samsung 860 PRO 1TB and "for Data Center" Samsung PM883 1TB both have about 1200 TBW lifespan, both cost about $180.
On the other hand 8-core Xeon 4215 is almost 2 times more expensive than 8-core consumer CPU but it has 3x the memory bandwidth (6 channel controller vs 2 channel), 1TB of RAM per processor vs 128GB, 48 PCIe lanes vs 20 and supports 2-way SMP. That means you can put few times more capacity (cores, memory, in 1U rack enclosure than with consumer hardware. That additional capacity can also share 1 PSU, 1 network card.
I'm not even talking about ECC memory and remote management capabilities available only in server grade hardware.
> (let alone SATA)
NVMe is (very) noticeably faster than SATA, especially for random IO, but also for sequential io patterns. Multiple queues and reduced protocol latency go a long way. SATA III throughput maxes out at 600 MB/s. In comparison, these drives do 4000-5000 MB/s.
avg-cpu: %user %nice %system %iowait %steal %idle
0.19 0.00 1.96 1.21 0.00 96.64
Device r/s rkB/s rrqm/s %rrqm r_await rareq-sz w/s wkB/s wrqm/s %wrqm w_await wareq-sz d/s dkB/s drqm/s %drqm d_await dareq-sz f/s f_await aqu-sz %util
nvme0n1 4180.00 332544.00 0.00 0.00 0.21 79.56 2518.00 1332796.00 74.00 2.85 6.89 529.31 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 18.21 81.60
it's wrapping code blocks :( you had one job.[1] https://www.tomshardware.com/news/intel-kills-off-all-optane...
It is important in compact builds.
Funnily enough, recent AMD CPUs for the consumer segment support ECC out of the box. But you need a right motherboard, of course. This is a welcome streak of sanity in the world where consumer PCs have 32GB RAM.
CPUs yes, but not APUs. This matters especially for SFF builds where you might not want a dGPU. For those, you specifically have to hunt for Ryzen Pro APUs which do have ECC support.
That's absolutely not true. I encourage you to re-read the article. The very specific case of qd=1 random reads are 4x (less than half what you suggest) faster, however in that scenario you probably care about latency more than speed. Also, qd=1 random reads are uncommon in disc-bound real-world scenarios.
There are plenty of benchmarks which have the optane close or losing, and as benchmarks become less synthetic the gaps largely disappear. The gains are marginal where they exist, and the price is outrageous. The problem is that optane is an appealing idea which simply failed to pan out.
905P is $598 for 480GB.
SN850 is $119 for 500GB.
https://www.anandtech.com/show/16558/micron-abandons-3d-xpoi...
Intel will need to bring Optane production in-house or get another partner on board if they're going to continue with it
I think the slot for a new NVRAM has gotten harder to fill. You almost have to sell it on read latency alone, because throughput (GB/s, parallel IOPS) is already high and scales with RAID, and most folks are either OK with Flash write latency or OK hiding it with (possibly powerloss-protected) DRAM buffers.
In a way maybe the easiest pitch is "instead of doubling your RAM, add 3x as much of this stuff," because relatively small caches can show real gains, so there isn't so much pressure on cost/GB. But it still has to be way cheaper than RAM and more performant than 'just' a great SSD.
And if the pitch is "replace your whole Flash array with this," beefy boxes tend to have TBs of Flash and most customers will only pay so much for improved latency, which puts a cap on the cost/GB of a commercially viable alternative SSD. Even the fastest Flash SSDs don't seem that popular!
A breakthrough could always happen, but I wonder if short-term we're looking more at progress through tweaks to the existing technologies rather than a leap to anything vastly different. If so that's largely because the current tech is pretty good, which is not the worst problem to have.
> In theory, the security guarantees offered by hardware encryption are similar to or better than software implementations. In reality, we found that many models using hardware encryption have critical security weaknesses due to specification, design, and implementation issues. For many models, these security weaknesses allow for complete recovery of the data without knowledge of any secret (such as the password). BitLocker, the encryption software built into Microsoft Windows will rely exclusively on hardware full-disk encryption if the SSD advertises support for it. Thus, for these drives, data protected by BitLocker is also compromised.
Source: Self-Encrypting Deception: Weaknesses in the Encryption of Solid State Drives (https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=883...)
> Changes the default setting for BitLocker when encrypting a self-encrypting hard drive. Now, the default is to use software encryption for newly encrypted drives. For existing drives, the type of encryption will not change.
Source: https://support.microsoft.com/en-us/topic/september-24-2019-...
edit: corrected below
( And still no roadmap of Affordable 10Gbps Ethernet, even 5Gbps would have been acceptable. But looks like we will only get 2.5Gbps as replacement. )
10Gbps right now is not expensive because it's expensive to implement, it's expensive because the royalties demanded by the patent holders are absurd. They are so bad they are probably counterproductive -- if they asked for less per port, it could have maybe ended up as the default standard on every device already, resulting in more royalties overall. In any case, the last relevant patent expires iirc summer of 2023, very soon after that there will be a lot of fast, cheap NICs, and soon after that, it will just be embedded into everything.
Edit: This? 2023-07-18
Adjusted expiration
edit: what where they thinking https://www.storagereview.com/wp-content/uploads/2020/11/Sto...
I have some similar graphs in my reviews, eg. [1], but to get something halfway neat and legible I have to limit how many drives are plotted at once and ensure the test stops when the drive reaches its limits. I also don't try to run this kind of test with a write workload against consumer drives, because it would require either heavily preconditioning the drives with enough writes to get SLC caching out of the picture, or using a ton of idle time to ensure each data point tested started from the same amount of cache available.
On some enterprise SSD reviews where it is actually appropriate to test them with random writes for days on end, I have produced graphs like [2], which are kinda messy but could be worse.
[1] https://images.anandtech.com/doci/16505/rr-rate-980pro-1000....
[2] https://images.anandtech.com/doci/15491/rw-clat_mean-p4800x-...
We need to start expressing write endurance as a multiple of write speed.
> We need to start expressing write endurance as a multiple of write speed
I can't tell if you're joking or not, but to be safe: no, we don't need to do that because there are virtually no realistic use cases where you'd continuously override data that you just stored on your persistent storage.
Rolling cache or a large number of camera feeds that you only want to keep for x duration.
Even a poorly-configured redis could do constant writes.
Honest question, this is (practically speaking) my impression after 20 years.
See https://www.anandtech.com/show/16458/2021-ssd-benchmark-suit... for more details. (Discussed at https://news.ycombinator.com/item?id=25994051 )
That's true, but there are multiple PCI-E 4.0 available on the market for a year already, with benchmarks available too..
both are selling at $199 from newegg right now...
but the WD sn850 blows away the 980 pro in nearly every benchmark.
I still have a greater degree of trust in Samsung for reliability and greatly exceeding their specified write-endurances (torture tests of MLC samsungs from 3 years ago illustrate that for a desktop workstation, you would have to REALLY abuse them to ever run into the write endurance problem).
I think they have some cache tuning differences, because while WD wins in many benchmarks by 30-40%, it losses the same 30-40% on long sequential writes.
I have no ssd expertise, so, can't comment why this could happen.
Shame more manufacturers don't make that type of drive
Now that Micron has apparently called it quits, it's a shame no manufacturers make that type of drive!
That's >2x higher throughput than an Optane at equivalent queue depth and (as far as I can see in the UK) at less than a tenth of the price: https://www.scan.co.uk/products/2tb-wd-black-sn850-m2-2280-p... vs https://www.scan.co.uk/products/15tb-intel-optane-dc-p4800x-...
And that's 7 GB/s from _one_ SSD. Aggregate memory bandwidth on something like the Zen3 is roughly 40 GB/s. These are also first generation PCIe 4, plenty more to come.
Doesn't require a huge improvement before you end up in a position where you simply don't have the memory bandwidth or cycles to deal with more than one drive.
I suspect the Optane wins most of the benchmarks because of it's outrageously good low queue depth random read performance - that's very effective for software that's not written for modern NVMe SSDs which benefit from very high queue depths. Check out the 4k random read performance from the SN850 at high queue depths:
https://images.anandtech.com/doci/16505/rr-s-sn850-1000.png
If you can keep the queues deep, it manages to beat the throughput of the Optane. You've got to design algorithms and data structures to exploit that kind of concurrency though.
You could also have IO storms with so many VMs, what if windows update start while 10 VMs kick of Ubuntu auto updates while at the same time a DB starts a backup job? In that case I don't want my web browser to slow down.
TL;DR: SSDs are harder to kill than they might seem.
The size of the dynamic SLC, when available, is roughly 1/3 of the erased space, with an upper bound.
If you don't need the capacity, set aside 30% of the drive in a partition you won't use, then use blkdiscard to erase it. Not only will this increase write performance, it may increase endurance. Increasing endurance with these drives is of interest because they are rated at 0.3 DWPD, compared to 1 DWPD with previous generation drives.
Taking over-provisioning to an extreme, I found that erasing a 980 Pro, then creating a 100 GB partition allowed me to overwrite that partition many times over at a sustained 5000 MB/s. This could be interesting for journaling, so long as you are ok with lack of power loss protection (unlikely for a journal) or cache flushes could be performed to ensure the data is on NAND, not just in DRAM.
But really, if you need to sustain writes at such a high rate, both of these are the wrong drive for endurance reasons. With optane stuck at PCIe gen 3, it may be great for low latency small blocks, but it won't exceed 3500 MB/s in a x4 NVMe form factor.
If you're still after endurance, low latency and a lot of random writes for journaling or a Bazel compiler cache, it seems like the P4801X is your best bet now, if you've got a 110mm NVMe slot.
I assume this is the recommended method for over-provisioning nowadays?
I've no idea where -- as it's been several years ago now -- but I can recall recommendations to use the HPA for this. I have no way to know, for certain, whether it actually helps but that's what I used to do (setting ~25% of the drive aside in the HPA). Anecdotally, I've yet to have such an SSD die on me, although I'm not exactly torturing them either.
Enterprise drives tend to allow namespace management. With such a drive you can delete the namespace that comes from the factory and create a smaller namespace or several smaller namespaces that have an aggregate capacity that leaves the desired over-provision space unallocated.
[1] https://www.samsung.com/semiconductor/global.semi.static/S19...