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 Application Configuration File
The configuration file mvmalloc.yml controls how the TMS library interacts with the system.

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 Application Configuration File

The configuration file mvmalloc.yml controls how the TMS library interacts with the system.

An example of the YAML-formatted file is shown here:

DpmeSocketName: /tmp/dpme_daemon.0
MallocCapture: true
MMapCapture: true
LogNamePrefix: /var/memverge/mvmalloc.log 
LogTrace: false
CommPort: 5678
DramTierGB: 16
HugePageDram: true

Two flags in mvmalloc.yml control which groups of glibc.so functions are intercepted by TMS:

MallocCapture: controls intercept of dynamic memory allocation functions.
MMapCapture: controls intercept of memory-mapped file I/O functions.

Setting either MallocCapture or MMapCapture to true causes all functions grouped within the setting to be intercepted and routed to TMS. See Intercepted Memory Functions.

If LogName is specified, Memory Machine writes to the named file. This means that multiple processes can write to the same file. To write to a separate log file for an application, use LogNamePrefix instead. With LogNamePrefix, Memory Machine appends the process ID and a unique identifier to the LogNamePrefix file path.

DramTierGB sets the application tier size. See Setting Volatile Tier Memory.

HugePageDram defines whether you are using HugePages for DRAM tier. See Configuring HugePages.