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).
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.
Configuring for Transparent Intercept
Loading Transparent Memory Service (TMS) before glibc.so requires changing the LD_PRELOAD environment variable.

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.
    - Intercepted Memory Functions
      The TMS library, mvmalloc.so, in Memory Machine supports a restricted set of glibc.so memory-management functions.
    - Configuring for Transparent Intercept
      Loading Transparent Memory Service (TMS) before glibc.so requires changing the LD_PRELOAD environment variable.
  - 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.
  - 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.

Configuring for Transparent Intercept

Loading Transparent Memory Service (TMS) before glibc.so requires changing the LD_PRELOAD environment variable.

TMS is implemented in a dynamic library named mvmalloc.so. To take advantage of TMS, LD_PRELOAD must be set to the filepath of mvmalloc.so. There are multiple ways to set LD_PRELOAD.

Memverge recommends using the script supplied with Memory Machine to set all required environment variables and run the application in one command. See Running an Application in Memory Machine. For information about setting the environment yourself, see Preparing to Run an Application.