How does PMEM operate in App Direct mode?
In App Direct Mode, Persistent Memory (PMEM) stops acting like a simple extension of RAM and starts acting like a high-speed, byte-addressable disk. It is the "gold standard" for 2026 database performance because it allows the application to control exactly where every byte is stored, ensuring it survives a power loss.
Here is the architectural journey of a data bit in App Direct Mode.
In App Direct Mode, the CPU and OS see two distinct types of memory:
Volatile Pool (DRAM): Your standard, ultra-fast RAM used for transient scratch space.
Persistent Pool (PMEM): A separate address space that looks like a "Block Device" (like an SSD) but responds like memory.
Unlike "Memory Mode," where DRAM hides the PMEM to act as a cache, in App Direct Mode, DRAM and PMEM work side-by-side. The application decides which data goes where.
The most critical feature of App Direct Mode is DAX. Normally, when an application reads from a "disk," the data must be copied into a temporary buffer in DRAM (the Kernel Page Cache).
With DAX, that copy step is deleted.
The database "Memory Maps" (mmap) a file directly from the PMEM device.
The CPU's Memory Management Unit (MMU) links the application's virtual address directly to the physical address on the PMEM DIMM.
When the app performs a LOAD or STORE, it talks directly to the persistent silicon. No kernel, no drivers, and no context switches.
In 2026, the biggest fear with App Direct Mode is data being stuck in the CPU cache when the power goes out. PMEM solves this through a hardware feature called Asynchronous DRAM Refresh (ADR).
The "Safe Zone": ADR ensures that the CPU's internal memory controller has enough residual power (via capacitors) to flush the "write pending" queues to the PMEM DIMMs during a power failure.
User Space Flushes: Applications use special instructions (like CLWB - Cache Line Write Back) to manually push data out of the CPU cache and into the ADR "Safe Zone." This ensures that when a database says a transaction is "Committed," it is physically permanent on the DIMM.
| Benefit | Impact on Oracle / SAP HANA |
| Instant Restart | Since data is already "in memory" and persistent, a 2TB database can "boot" in seconds—no need to read blocks from an SSD. |
| Zero-Copy I/O | The database buffer cache can reside directly on PMEM, eliminating the overhead of moving data between RAM and Disk. |
| Byte-Granularity | You can update a single 8-byte pointer without writing a whole 4KB or 8KB block, drastically reducing "Write Amplification." |
To use App Direct Mode in OCI, your stack looks like this:
Hardware: PMEM DIMMs in App Direct Mode (configured in BIOS).
OS: Linux with ndctl and daxctl utilities.
Filesystem: XFS or EXT4 mounted with the -o dax option.
Application: "PMEM-Aware" software (Oracle 19c/21c+, SAP HANA, or Redis-PMEM).
"In App Direct Mode, the line between memory and storage doesn't just blur—it disappears. You treat your storage exactly like your RAM, but with the peace of mind that it won't vanish when the lights go out."