Skip to content

sql-server-linux-configure-pmem.md

Latest commit

 

History

History
89 lines (64 loc) · 3.8 KB

sql-server-linux-configure-pmem.md

File metadata and controls

89 lines (64 loc) · 3.8 KB
title Configure persistent memory (PMEM)
description Learn how to configure persistent memory (PMEM) for SQL Server on Linux, as well as how to create namespaces for PMEM devices.
ms.custom seo-lt-2019
author briancarrig
ms.author brcarrig
ms.date 10/31/2019
ms.topic conceptual
ms.prod sql
ms.technology linux
monikerRange >= sql-server-linux-ver15 || >= sql-server-ver15

Configure persistent memory (PMEM) for SQL Server on Linux

[!INCLUDE SQL Server - Linux]

This article describes how to configure the persistent memory (PMEM) for [!INCLUDEsqlv15] on Linux.

Overview

[!INCLUDEsqlv15] has a number of in-memory features that use persistent memory. This document covers the steps required to configure persistent memory for SQL Server on Linux.

Note

The term enlightenment was introduced to convey the concept of working with a persistent memory aware file system. Direct access to the file system from user-space applications is facilitated using memory mapping (mmap()). When a memory mapping for a file is created the application can issue load/store instructions bypassing the I/O stack completely. This is considered an "enlightened" file access method from the perspective of the host extension application (which is the black box code that allows SQLPAL interact with the Windows or Linux OS).

Create namespaces for PMEM devices

Configure the devices

In Linux, use the ndctl utility.

  • Install ndctl to configure PMEM device. You can find it here.
  • Use ndctl to create a namespace. Namespaces are interleaved across PMEM NVDIMMs and can provide different types of user-space access to memory regions on the device. fsdax is default and desired mode for SQL Server.
ndctl create-namespace -f -e namespace0.0 --mode=fsdax* --map=dev

Note that we have chosen fsdax mode and are using system memory to store per-page metadata. We recommend using --map=dev. This stores the meta data on the namespace directly. Storing meta data in memory using --map=mem is considered experimental at this time.

Use ndctl to verify the namespace.

Sample output follows:

# ndctl list -N
{
  "dev":"namespace0.0",
  "mode":"fsdax",
  "map":"dev",
  "size":4294967296,
  "sector_size":512,
  "blockdev":"pmem0",
  "numa_node":0
}

Create and mount PMEM device

For example, with XFS

mkfs.xfs -f /dev/pmem0
mount -o dax,noatime /dev/pmem0 /mnt/dax
xfs_io -c "extsize 2m" /mnt/dax

For example, with EXT4

mkfs.ext4 -b 4096 -E stride=512 -F /dev/pmem0
mount -o dax,noatime /dev/pmem0 /mnt/dax

Technical considerations

  • Block allocation of 2MB for either XFS/EXT4, as described above
  • Misalignment between block allocation and mmap results in silent fallback to 4KB
  • File sizes should be a multiple of 2MB (modulo 2MB)
  • Do not disable transparent huge pages (THP) (enabled by default on most distros)

Once the device has been configured with ndctl, created, and mounted, you can place database files in it or create a new database.

Because PMEM devices are O_DIRECT (direct I/O) safe, consider enabling trace flag 3979 to disable the forced flush mechanism. For more information see FUA support. Forced unit access internals are covered here FUA internals.

Next steps

For more information about SQL Server on Linux, see SQL Server on Linux. For performance best practices for SQL Server on Linux, see Performance Best Practices.