Home
Overview and Installation
Getting started with MemVerge Memory Machine requries that you understand some background information about how persistent memory works. You can then install Memory Machine on a server and begin monitoring memory usage and capturing application snapshots.
Introduction to MemVerge Memory Machine
MemVerge Memory Machine (Memory Machine) enables applications to expand from volatile memory (DRAM) into persistent memory (PMEM).
The Distributed Persistent Memory Engine
MemVerge Distributed Persistent Memory Engine (DPME) is at the heart of Memory Machine. DPME manages memory allocation to volatile memory (DRAM) and persistent memory (PMEM) for all applications run under Memory Machine.

Overview and Installation
Getting started with MemVerge Memory Machine requries that you understand some background information about how persistent memory works. You can then install Memory Machine on a server and begin monitoring memory usage and capturing application snapshots.
- Introduction to MemVerge Memory Machine
  MemVerge Memory Machine (Memory Machine) enables applications to expand from volatile memory (DRAM) into persistent memory (PMEM).
  - Introduction to PMEM
    Using volatile memory (DRAM) and persistent memory (PMEM) in combination enables applications to expand memory capacity relatively cheaply and to persist memory data objects, a capability that previously was only possible by writing to storage devices.
  - Transparent Memory Service
    The Transparent Memory Service (TMS) intercepts Linux glibc.so function calls and reroutes them to the Distributed Persistent Memory Engine (DPME), which manages the MemVerge PMEM store.
  - The Distributed Persistent Memory Engine
    MemVerge Distributed Persistent Memory Engine (DPME) is at the heart of Memory Machine. DPME manages memory allocation to volatile memory (DRAM) and persistent memory (PMEM) for all applications run under Memory Machine.
    - The Application DRAM Tier
      To take advantage of the speed of volatile memory (DRAM), the Distributed Persistent Memory Engine (DPME) moves the most in-demand memory pages to the local machine’s DRAM in a process called tiering.
    - DRAM Tier Management Policy
      Memory Machine moves data from PMEM to a DRAM tier to improve memory performance. The DRAM tier is managed using a Least Recently Used (LRU) policy.
    - NUMA Allocation of PMEM
      DPME allocates PMEM to the NUMA node running the allocating process whenever possible.
  - Memory Machine Management Service
    Memory Machine Management Service (Management Service) runs alongside the Memory Machine data serivce to handle tasks not having to do with application data.
  - Understanding Snapshots
    A snapshot is a static image of a running application's process tree. You can use Memory Machine ZeroIO Snapshot to almost instantly capture a snapshot, then later just as quickly restore the running process to the state captured in the snapshot.
- Getting Started with Memory Machine
  You run Memory Machine on a host equipped with one or more PMEM devices.
Using the Memory Machine Management Center
Memory Machine Management Center (M3C) is a web UI application available on the host that is running the Memory Machine Management Service. You can view system resources and performance metrics; create and restore snapshots; schedule jobs; and more in M3C.
Using the Command Line Interface
You can administer and use MemVerge Memory Machine using the Command Line Interface (CLI) on any installed host.
Working with Applications
MemVerge provides additional instructions for some popular applications supported by Memory Machine, either to assist with complex setup or to support additional functionality.
All Documentation
Links to documentation for all releases of MemVerge Memory Machine.

The Distributed Persistent Memory Engine

MemVerge Distributed Persistent Memory Engine (DPME) is at the heart of Memory Machine. DPME manages memory allocation to volatile memory (DRAM) and persistent memory (PMEM) for all applications run under Memory Machine.

DPME maps programmatic memory calls to the MemVerge PMEM store. You must start the DPME process, mvmallocd, on the application server to take advantage of MemVerge PMEM memory management. See Starting Data Services.

DPME does the following:

Allocates and deallocates PMEM among multiple running processes
Manages PMEM by implementing copy-on-write
Manages DRAM for applications that return all of their PMEM upon termination
Supports ZeroIO Snapshot technology by managing snapshots in PMEM
Provides information and statistics on PMEM usage