HMB, or Host Memory Buffer, is an NVMe feature that lets a DRAM-less SSD borrow a small slice of your computer’s own system RAM to store its mapping table, instead of carrying a dedicated DRAM chip onboard. It is how budget NVMe drives approach the responsiveness of pricier DRAM-equipped drives without the extra manufacturing cost. HMB requires NVMe driver support to actually work.
The Problem HMB Solves
As covered in the companion article on DRAM cache and DRAM-less drives, every SSD needs fast access to a mapping table that tracks where each piece of data actually sits on the flash. Drives with dedicated DRAM keep that table in fast, purpose-built memory right next to the controller. Drives without DRAM have to put the table somewhere else — and storing the whole thing on the NAND flash itself is slow, since flash reads take meaningfully longer than DRAM reads and every lookup competes with actual data traffic.
HMB gives DRAM-less drives a third option: reach across the PCIe bus and use a small piece of the host computer’s system memory as if it were the drive’s own cache.
How HMB Works, Mechanically
HMB is defined as part of the NVMe specification (introduced in NVMe 1.2). During initialization, an HMB-capable SSD requests an allocation of host memory from the operating system’s NVMe driver. If the driver grants it, the drive uses that reserved region — typically a modest slice of system RAM — to hold some or all of its mapping table, the same job dedicated DRAM would otherwise do. The allocation is negotiated at boot and is exclusive to the drive for as long as the system is running; it is released back to the operating system if the drive is removed or the allocation is revoked.
This is a cooperative feature, not a guarantee. The drive requests a buffer; the host decides whether, and how much, to grant, based on available system memory and driver support.
What HMB Needs From Your System
For HMB to actually engage, three things need to line up:
- An NVMe drive that supports it — most modern DRAM-less NVMe drives do, including budget lines like the Crucial P310 500GB Gen4 NVMe and the Western Digital SN580 2TB NVMe Gen4.
- An NVMe driver that supports HMB — current Windows, macOS, and Linux NVMe drivers all support it; very old or minimal third-party NVMe drivers occasionally do not.
- Available system RAM — a low-memory system under heavy load could see the OS decline or shrink the requested allocation, though this is uncommon on typical modern configurations.
If any of those conditions is not met, the drive falls back to managing its mapping table from flash alone, which still works — just with somewhat higher lookup latency under heavy random-access workloads.
HMB vs. Real DRAM: The Performance Reality
System RAM reached over PCIe via HMB is still slower than a dedicated DRAM chip sitting directly next to the controller, simply because of the extra bus hop involved. In practice, that gap is mostly invisible in everyday use: sequential transfers, general application loading, and typical desktop multitasking show little difference between a well-implemented DRAM-less-plus-HMB drive and a DRAM-equipped one.
The gap widens under sustained heavy random I/O — large database workloads, or many simultaneous demanding processes hammering the drive at once — where dedicated DRAM’s consistently lower latency and lack of dependency on host memory availability give it a real edge. For the specifics of which workloads land on which side of that line, see the DRAM-versus-DRAM-less comparison above.
Spotting an HMB Drive When Shopping
Manufacturers rarely lead with "DRAM-less" in marketing copy, but a mention of HMB support in the spec sheet is a reliable signal that a drive skips dedicated DRAM. It shows up most often in:
- Entry and budget tiers of a manufacturer’s NVMe lineup, positioned below their flagship or "Pro" models
- Compact and power-conscious form factors, including many laptop-oriented and single-sided M.2 drives, where every square millimeter and milliwatt is contested
- Independent SSD reviews and controller teardowns from established hardware outlets, which typically confirm HMB support and DRAM presence directly
Frequently Asked Questions
Does HMB use up my computer’s RAM permanently?
No. The allocation is reserved only while the drive is active and in use; it is a small, negotiated slice of memory rather than a permanent reduction in available system RAM for other applications.
Can I turn HMB on or off?
Not typically through user-facing settings — it is negotiated automatically between the drive and the NVMe driver at boot. Manufacturer utility software occasionally exposes drive health details, but HMB negotiation itself is not a user-toggled feature on consumer systems.
Is a drive with HMB the same thing as a DRAM-less drive?
Nearly always — HMB exists specifically because a drive lacks dedicated DRAM. A DRAM-equipped drive has no need for HMB, since it already has fast onboard memory for its mapping table.
Will an HMB drive work in an older system without NVMe driver support?
The drive itself will still function — HMB is a performance optimization, not a requirement for basic operation. Without a supporting driver, the drive simply falls back to managing its mapping table from flash alone.
Share this article: Twitter