What "DRAM-less" actually costs you
Every SSD keeps a map that links the logical addresses your operating system uses to the physical flash locations holding the data. Drives with onboard DRAM keep much of that map on a fast chip. DRAM-less drives can't, so on a cache miss the controller has to go back to the slower NAND. Without dedicated DRAM for the address mapping table, the controller must repeatedly read that table from slower NAND flash on a cache miss.
NVMe drives have a workaround called Host Memory Buffer (HMB). A peer-reviewed 2020 PLOS ONE study found that commercial DRAM-less SSDs clearly performed worse than drives with internal DRAM, but HMB improved that. The same study found that the drives it tested mainly used the host memory buffer as an address-mapping-table cache, not as a read cache or write buffer.
HMB helps. It does not turn a cheap drive into a premium one. Some practical caveats from the search results:
- Operating system support matters. One industry write-up says HMB is generally enabled by Windows 10 and later and by modern Linux NVMe drivers when the drive and platform support it. The same source notes that a claim about newer Windows 11 builds allowing larger buffers comes from specialist reporting, not a Microsoft specification.
- Enclosures can break it. A Digiera explainer says a DRAM-less NVMe drive in a USB enclosure usually loses HMB, so it can feel much slower than it did inside a PC. Treat that as a retailer's claim, not a lab result, but it fits the logic of the feature. It is worth remembering for job number four.
- Not every drive is equal. Reviewers warn that a weak DRAM-less design paired with aggressive QLC can feel sluggish when you copy a big project folder.
The six jobs
1. Reviving an aging desktop or laptop
This is the strongest case. If the old machine has a mechanical hard drive, any SSD is a big step up. Even a bargain SATA model will do. White's argument is that an ancient PC can't exploit what a better drive offers anyway, so the missing DRAM costs you nothing you would have noticed.
If the machine supports NVMe, a DRAM-less NVMe drive with HMB is the better pick. Check the interface, the physical fit and operating system support first. White offers no before-and-after benchmarks, and I won't invent any. The jump from HDD to SSD is large enough to feel without a stopwatch.
2. Storing a Steam game library
Games mostly read. Installing a huge title will stress a budget drive's write behavior, but you do that once. After that, loading is largely sequential and random reads, which DRAM-less drives handle acceptably.
One caveat is worth adding. A How-To Geek piece on HMB drives reports that a TechPowerUp review of one QLC DRAM-less model found its main weakness was sustained write performance, which drops to around 400MB/s once the SLC cache fills. That is one drive, not all of them. It does explain why a big install can take a bit longer than the spec sheet suggests. A game library tolerates that. A video-editing scratch disk would not.
3. Upgrading a Steam Deck
White points out that the Deck's internal SSD interface tops out at PCIe 3.0. A faster PCIe 4.0 drive therefore gains you nothing in speed. You do get capacity, which for a handheld matters more.
The form factor is the part to get right. iFixit's guide states that the Steam Deck's SSD is a single-sided M.2 2230. That is why a standard 2280 desktop drive won't fit. Note that iFixit's page covers the LCD model and sends OLED owners to a separate guide.
Don't treat this as a simple plug-in swap. iFixit rates the job moderate and estimates 20 minutes to an hour. Its procedure includes these steps:
- Let the battery drain below 25% before you start.
- Remove the microSD card, which iFixit warns can snap if you pull the back cover with it still installed.
- Take off the back cover and the board shield, then disconnect the battery.
- Remove one screw and swap the drive.
iFixit also says Valve recommends putting the Deck into battery storage mode in the BIOS before any internal repair. You will also need to reinstall the operating system. iFixit says to follow Valve's recovery instructions to re-image the drive with SteamOS. It adds that the buttons and touchpads may not respond at first after re-imaging, so use the touchscreen during initial setup.
4. Turning it into a portable SSD
Put an old drive in an enclosure and you have cheap portable storage. For moving files around, White says almost any old SSD will do. The catch is that your real speed is set by the slowest link in the chain: the drive, the enclosure's bridge chip, the cable and the computer's port.
ASUS support gives a concrete example. A USB 3.2 Gen 1 port tops out at 5Gb/s theoretically, and Gen 2 Type-C reaches 10Gb/s theoretically. A drive rated for several gigabytes per second won't get near that through a Gen 1 port.
Buy an enclosure that matches your drive type, because SATA M.2 and NVMe are different. Combine that with the HMB caveat above. And a portable SSD is not a backup. It is a second copy at best.
5. Holding a Plex or Jellyfin media library
Video playback is mostly sequential reading, so a DRAM-less SSD handles it easily. The drive is rarely the bottleneck. Plex's documentation says a server is generally limited by processor power, network speed and storage space. Transcoding load comes mainly from the CPU, not the disk.
Plex also notes that average bitrate is a poor guide to streaming needs, because video bitrate spikes during complex scenes. That affects your network and transcoder more than your storage.
Jellyfin's documentation adds a useful rule: keep the Jellyfin database on local storage, not on a network device. It also says a database for a moderate-sized library can grow from 10 to 100 GB, and that the transcoding folder needs about as much space as the original media at an equivalent bitrate. So an SSD for metadata and app files is a sound idea. Size it with those numbers in mind.
White concedes the economics: for terabytes of movies, a hard drive still costs less per terabyte.
6. A lightweight boot drive for a mini PC or homelab
If the box boots Linux and runs Pi-hole or a few small Docker containers, a spare DRAM-less drive is plenty. Pi-hole's documentation lists modest requirements: 512MB of RAM and a minimum of 2GB of free space. It also says you are not limited to a Raspberry Pi, so an old mini PC works fine.
The limit is write intensity. White says outright that a bargain drive isn't great for write-heavy databases. Endurance depends on the NAND type, capacity, controller and firmware, not just on whether a DRAM chip is present. Don't assume a DRAM-less drive is fragile, and don't assume a drive with DRAM is immortal.
Quick fit guide
| Job | Workload type | DRAM-less verdict |
|---|---|---|
| Old PC upgrade | Mixed, light | Good, especially replacing an HDD |
| Game library | Read-heavy | Good; installs may be slower |
| Steam Deck | Read-heavy, PCIe 3.0 limit | Good; needs single-sided 2230 |
| Portable SSD | Transfers | Fine; check HMB and port limits |
| Plex/Jellyfin | Sequential reads | Good; the CPU and network matter more |
| Homelab boot drive | Light writes | Fine; avoid write-heavy databases |
The takeaway
"DRAM-less" describes a design choice. It is not a quality grade. The pattern across all six jobs is the same: read-heavy or lightly written workloads on secondary or older systems. Those are the jobs where a missing cache rarely matters.
There is also a fair counterpoint. Not everyone is as relaxed about these drives as White. The research literature is clear that DRAM-less drives lose to DRAM drives in some measurements, and HMB's benefit depends on the drive, firmware and host. The sensible approach is to match the drive to the job. Don't pick the drive and then hope.
If you have a spare one in a drawer, one of these six jobs is probably waiting for it. White's closing line puts it well: an SSD with a job beats one collecting dust.
References
- 6 jobs a cheap DRAM-less SSD can still handle without breaking a sweat How-To Geek · 2026-11-19T22:30:15+00:00
- Steam Deck SSD Replacement - iFixit Repair Guide ifixit.com
- Server Settings - Bandwidth and Transcoding Limits | Plex Support support.plex.tv