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 Control Path Service
The Control Path Service (CPS) is a management service (as opposed to a data service) that manages aspects of Memory Machine not having to do with data.

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.
  - Differences Between Memory Machine Editions
    Memory Machine is available in two editions, Standard Edition for managing memory on individual hosts and Advanced Edition for managing clusters of hosts at the enterprise level.
  - 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 Control Path Service
    The Control Path Service (CPS) is a management service (as opposed to a data service) that manages aspects of Memory Machine not having to do with 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 Dashboard
You can view system resources and performance metrics, and create and restore snapshots in MemVerge Memory Machine using the Memory Machine Dashboard, a web UI application running on one of the installed hosts.
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.

The Control Path Service

The Control Path Service (CPS) is a management service (as opposed to a data service) that manages aspects of Memory Machine not having to do with data.

CPS runs as a service daemon named mmctl. Functions handled by CPS include:

Running the web server for Memory Machine Dashboard
Servicing API requests
Managing and storing configurations
Gathering metrics
Generating logs
Generating a monthly usage report for billing
Communicating with MemVerge if Call Home is active
Managing scheduled jobs such as scheduled snapshots

For the most part these functions do not concern the user, but you should be aware that CPS exists and needs to be running on Memory Machine. See Running the Control Path Service.