Tuning Suggestions for Common Scenarios

Enable the madvise mode so that huge pages can be used only when necessary.

echo madvise > /sys/kernel/mm/transparent_hugepage/enabled

Use defer+madvise for memory defragmentation in the background only for explicit requests.

echo defer+madvise > /sys/kernel/mm/transparent_hugepage/defrag

Databases such as MySQL, PostgreSQL, and Redis are sensitive to performance jitter. You are advised to disable THP.

echo never > /sys/kernel/mm/transparent_hugepage/enabled

To permanently disable THP, add the following information to startup parameters:

sudo grubby --args="transparent_hugepage=never" --update-kernel="/boot/vmlinuz-$(uname -r)" sudo reboot

If the CPU usage of the khugepaged daemon is high, you can use the following settings to reduce the activity of khugepaged.

Reduce the scanning frequency of khugepaged.

echo 30000 > /sys/kernel/mm/transparent_hugepage/khugepaged/scan_sleep_millisecs

Increase the retry interval between two allocation attempts.

echo 120000 > /sys/kernel/mm/transparent_hugepage/khugepaged/alloc_sleep_millisecs

Reduce the number of pages scanned each time.

echo 2048 > /sys/kernel/mm/transparent_hugepage/khugepaged/pages_to_scan

Disable automatic defragmentation of khugepaged (if necessary).

echo 0 > /sys/kernel/mm/transparent_hugepage/khugepaged/defrag

Parent topic: Tuning of Transparent Huge Pages

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.