Home
Overview and Installation
Understanding how persistent memory works is helpful when getting started with MemVerge Memory Machine. 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 MemVerge Memory Allocation Service
MemVerge MemVerge Memory Allocation Service (MVMAS) is at the heart of Memory Machine. MVMAS 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 MemVerge Memory Allocation Service (MVMAS) moves the most in-demand memory pages to the local machine’s DRAM in a process called tiering.

Overview and Installation
Understanding how persistent memory works is helpful when getting started with MemVerge Memory Machine. 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 MemVerge Memory Allocation Service (MVMAS), which manages the MemVerge PMem store.
  - The MemVerge Memory Allocation Service
    MemVerge MemVerge Memory Allocation Service (MVMAS) is at the heart of Memory Machine. MVMAS 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 MemVerge Memory Allocation Service (MVMAS) 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.
    - Automatic DRAM Tier Sizing
      Memory Machine can automatically reallocate DRAM tier while an application is running.
    - NUMA Allocation of PMem
      MVMAS 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 service 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 Tools
You can administer and use MemVerge Memory Machine using a Command Line Interface (CLI).
Memory Machine Administration
MemVerge Memory Machine can be installed and run using CLI commands. Many administrative tasks can be performed using the Memory Machine Management Center web interface.
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.

The Application DRAM Tier

To take advantage of the speed of volatile memory (DRAM), the MemVerge Memory Allocation Service (MVMAS) moves the most in-demand memory pages to the local machine’s DRAM in a process called tiering.

In tiering, the MVMAS moves pages that are more frequently or recently used by the application to the faster DRAM tier and "evicts" less recently or frequently used data to PMem. See tiering.

The DRAM tier space is allocated from a shared memory pool, so over-allocating DRAM tier memory for a Memory Machine application could degrade performance or cause failure of other server processes. Conversely, under-allocating DRAM tier could hinder the application's performance. See Setting DRAM Tier Memory.

MVMAS greatly increases performance by using 2MB HugePage translation lookaside buffer (TLB) pages to tier data between PMem and DRAM. To gain these performance advantages, you must allocate a HugePages pool on the server. See Configuring HugePages.