Home
Using the Command Line Interface
You can administer and use MemVerge Memory Machine using the Command Line Interface (CLI) on any installed host.
Managing Application Memory
To manage application memory with Memory Machine, you run the application on a data host in an environment with Transparent Memory Service (TMS) and Distributed Persistent Memory Engine (DPME).
Using Containers with Memory Machine
You can configure Memory Machine to manage memory for containers running in OpenShift or Kubernetes.
Configuring PMEM

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.
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 Interface
You can administer and use MemVerge Memory Machine using the Command Line Interface (CLI) on any installed host.
- MemVerge Memory Machine Administration
  MemVerge Memory Machine can be installed and run using CLI commands.
- Managing Application Memory
  To manage application memory with Memory Machine, you run the application on a data host in an environment with Transparent Memory Service (TMS) and Distributed Persistent Memory Engine (DPME).
  - Calculating Process Count Limits
  - Running an Application in Memory Machine
    To run an application with Memory Machine memory management, use the mm script supplied with Memory Machine.
  - Stopping an Application Instance
    Stop an application instance in whatever manner is recommended for the application you are running.
  - Configuring Application Memory
    Configure managed memory to optimize for individual application instances. You can do this by setting the size of DRAM Tier and configuring Linux HugePages. To facilitate experimentation, these adjustments can be made "on the fly" while the application instance is running.
  - Using Containers with Memory Machine
    You can configure Memory Machine to manage memory for containers running in OpenShift or Kubernetes.
    - The Memory Machine Container Model
      To manage containers, Memory Machine runs in a single pod on each container node and manages memory in a local persistent volume (PV). Application container pods on that node mount the PV to gain access to managed memory.
    - Container Management Overview
      To manage containers in Memory Machine, deploy a Kubernetes or OpenShift® cluster and deploy Memory Machine on the cluster.
    - Configuring the Container Manager
      Configure access to the Memory Machine OpenShift or Kubernetes packages.
    - Configuring HugePages
    - Configuring PMEM
    - Deploying the Container Webhook
    - Deploy the DaemonSet
    - Testing the Container Setup
- Using Snapshots in the Memory Machine CLI
  Use the mvmcli snapshot command from the CLI on a Memory Machine host to capture the state of a running process, then later restore the running process to the captured state.
- Troubleshooting
- Preparing Intel® Optane™ DC Persistent Memory PMEM
  Prepare PMEM for use by configuring the Intel Optane DC Direct Access (DAX) devices in AppDirect mode.
- Preparing to Run an Application
  Normally you run applications by using the mm wrapper script supplied with Memory Machine. See oxy_ex-3/topics/t_mvmm_running_an_application_with_mvmm.html. If you do not use the mm to run your application, you must set up the Memory Machine environment manually before running the application.
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.
All Documentation
Links to documentation for all releases of MemVerge Memory Machine.

Configuring PMEM

About this task

This procedure describes how to create a pod to contain the DPME. This must be done on each container node.

Label all nodes that have PMEM

$ kubectl label node <node_name> storage=pmem

Procedure

Label all nodes that have PMEM:

$ kubectl label node node_name storage=pmem

On each container node, use the supplied script to create a pmem-fsdax-config run-once daemonSet:

$ scripts/config-pmem.sh
daemonset.apps/pmem-fsdax-config created
waiting for pmem-fsdax-config pods to run....
waiting for pmem-fsdax-config daemonset to complete
Successfully configured PMEM namespace to fsdax
daemonset.apps "pmem-fsdax-config" deleted
$

Optional: Change the PMEM file size for the containerized DPME.
1. To change the PMEM file size for mvmallocd, modify the sudo fallocate line in mount.sh:
```
sudo fallocate -l PMEM_size /mnt/pmem${numa}/mm
```
Where PMEM_size is the required size suffixed with G for gigabytes. For example: 16G.

Important:
The PMEM file size must be less than the VM PMEM capacity.

For example, if you assigned less than 16G PMEM to a VM, change the fallocate size to be less than this capacity:
```
sudo fallocate -l 12G /mnt/pmem${numa}/mm
```
Associate the VM with specific NUMA node as recommended by VMware. See "Associate Virtual Machines with Specified NUMA Nodes" on the VMware documentation website.
Associate PMEM allocation for that VM to the same NUMA node. See VMware knowledge base article 78094.
Run mount.sh. This script takes two optional arguments: --ssh-key-path and --nvdimm:
Run the mount script:
```
$ scripts/mount.sh --ssh-key-path ssh_key_path \
--nvdimm nvdimms
$
```
Where

--ssh-key-path

is the path to SSH private key file.

--nvdimm

is the number of NVDIMMs on each container node. Default value is one.

Both parameters are optional.

Verify that the PMEM device is mounted on each container node:

$ ssh -i ssh_key_file core@node_ip
[core@node_ip ~]$ df -h
Filesystem                            Size  Used Avail Use% Mounted on
...
/dev/pmem0                            32G   42M   32G   1% /var/mnt/pmem0
...
$