Transparent huge memory pages and Splunk performance

Some distributions of Linux (for example, Red Hat, CentOS, and Ubuntu) have an advanced memory management scheme called Transparent Huge Pages (THP). THP acts as an abstraction layer that lets the memory management units (MMUs) in a Linux system work with huge memory pages. With THP, this work occurs without specific action on the behalf of the administrator or the software that runs on the host.

Every CPU in a modern machine has an MMU. The MMU manages memory in pages, and huge pages are structures that let MMUs manage multiple gigabytes and terabytes of memory more efficiently.

THP has been associated with degradation of Splunk Enterprise performance in at least some Linux kernel versions. When enabled, THP can significantly degrade overall machine performance on systems that run Splunk Enterprise because of several issues:

• The implementation is too aggressive at coalescing memory pages for short-lived processes (such as many Splunk searches)
• It can prevent the jemalloc memory allocation implementation from releasing memory back to the operating system after use. The jemalloc implementation is more scalable version of the malloc implementation and has been used in newer distributions of Linux.
• For some workloads, it can cause I/O regressions surrounding swapping of huge pages.

Splunk has observed a minimum of a 30% degradation in indexing and search performance on Linux systems where THP is active, with a similar percentage increase in latency. Where possible, turn off THP on your Linux system configuration for all machines that run Splunk software, unless that machine also runs an application that requires THP.