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.
Getting Started with Memory Machine
You run Memory Machine on a host equipped with one or more PMEM devices.
Configuration Files
MemVerge Memory Machine uses several YAML-formatted configuration files. Two of these, mvmallocd.yml and mvmalloc.yml contain user-configurable parameters.
The Distributed Persistent Memory Engine Configuration File

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).
- Getting Started with Memory Machine
  You run Memory Machine on a host equipped with one or more PMEM devices.
  - Hardware Recommendations
  - Network Recommendations
    For optimal performance and consistency throughout the Memory Machine System, MemVerge either requires or recommends specific values for open port numbers, communication protocols, and other network-related configurations.
  - Software Recommendations
    MemVerge recommends that you conform to software dependencies, such as operating systems and packages, that have been tested with MemVerge products.
  - Installing MemVerge Memory Machine
    Install MemVerge Memory Machine (Memory Machine) data service on all hosts requiring memory management.
  - Configuration Files
    MemVerge Memory Machine uses several YAML-formatted configuration files. Two of these, mvmallocd.yml and mvmalloc.yml contain user-configurable parameters.
    - The Memory Machine Configuration File
    - The Distributed Persistent Memory Engine Configuration File
    - The Application Configuration File
      The configuration file mvmalloc.yml controls how the TMS library interacts with the system.
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 Distributed Persistent Memory Engine Configuration File

The Distributed Persistent Memory Engine (DPME) configuration file contains information about the server's PMEM that DPME requires to run. Most important are the names of the DAX devices that contain the PMEM. The names are in the form: /dev/device_name:numa_node, where numa_node defines which NUMA node the device is associated with.

The NUMA node can be supplied so that DPME does not reassign a DAX device to a different NUMA node on reboot.

If you don't provide the NUMA node, DPME uses the ndctl utility to automatically determine the NUMA node. You only need to supply the NUMA node if ndctl is not present or if you need to override the value supplied by ndctl.

If you do not supply the NUMA node, leave off both the colon and the value. For example: /dev/dax/1.0 instead of /dev/dax1.0:1

The DPME configuration file also contains startup parameters that control such things as logging, debugging, and licensing for the DPME engine.

Following is an example DPME configuration file.

PMEM: /dev/dax0.0:0       #  <name> = /dev/dax0.0,  <numa_node> = 0
PMEM: /dev/dax0.1:1
Trace: false