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.

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.

Configuration Files

MemVerge Memory Machine uses several YAML-formatted configuration files. Two of these, mvmallocd.yml and mvmalloc.yml contain user-configurable parameters.

These files contain YAML formatted configuration information:

mm.yml: is the Memory Machine configuration file.; Important: Do not modify mm.yml.
mmagent.yml: is the configuration file for the Memory Machine Agent.; Important: Do not modify mmagent.yml.
mmctl.yml: is the configuration file for the Control Path Service.; Important: Do not modify mmctl.yml.
mvcsnapd.yml: is the configuration file for the MemVerge cluster snapshot service.; Important: Do not modify mvcsnapd.yml.
mvmallocd.yml: is the configuration file for the Distributed Persistent Memory Engine (DPME). See The Distributed Persistent Memory Engine.
mvmalloc.yml: is the application configuration file. This file controls how unmodified applications use Memory Machine to allocate persistent memory. This file can be copied and modified to apply different configurations to application instances. See Configuring for Transparent Intercept.

Besides the YAML files, the file /etc/memverge/mvmlog_groom.list contains the names of log files that Memory Machine periodically cleans up by removing the oldest records.

Important: Do not confuse the mvmalloc.yml and mvmallocd.yml files. Despite their similar names, they are two distinct configuration files.