Red Hat Enterprise Linux 6 7關閉透明大頁面及透明大頁面基礎概念
環境
- Red Hat Enterprise Linux (RHEL) 6
- Red Hat Enterprise Linux (RHEL) 7
問題
- How do transparent hugepages work in RHEL 6?
- How are transparent hugepages activated by a process?
- Do we still need to preallocate some amount of memory for use as (transparent) hugepages?
- How can I see the number of transparent hugepages that are actually in use on the system (either globally or by individual processes)?
- How do I enable HugePages on Red Hat Enterprise Linux?
- How do I disable HugePages on Red Hat Enterprise Linux?
- Freezing issue while streaming out from RHEL 6.2 server, We are providing a streaming platform (RTSP, HLS) to our customers, based on RHEL 6.2 x86_64
While streaming out, we experiencing delays (more than one to ten seconds) because of a process freeze and at the same point in time a bunch of memory is being freed - Need assistance to Disable Transparent Huge Pages (THP) in RHEL 7.4
決議
Note:
Transparent Huge Pages are
.
For RHEL 7 see
For RHEL 8 see
Transparent Huge Pages (THP) are enabled by default in RHEL 6 for all applications. The kernel attempts to allocate hugepages whenever possible and any Linux process will receive 2MB pages if the mmap region is 2MB naturally aligned. The main kernel address space itself is mapped with hugepages, reducing TLB pressure from kernel code. For general information on Hugepages, see:
The kernel will always attempt to satisfy a memory allocation using hugepages. If no hugepages are available (due to non availability of physically continuous memory for example) the kernel will fall back to the regular 4KB pages. THP are also swappable (unlike hugetlbfs). This is achieved by breaking the huge page to smaller 4KB pages, which are then swapped out normally.
But to use hugepages effectively, the kernel must find physically continuous areas of memory big enough to satisfy the request, and also properly aligned. For this, a khugepaged kernel thread has been added. This thread will occasionally attempt to substitute smaller pages being used currently with a hugepage allocation, thus maximizing THP usage.
In userland, no modifications to the applications are necessary (hence transparent). But there are ways to optimize its use. For applications that want to use hugepages, use of posix_memalign() can also help ensure that large allocations are aligned to huge page (2MB) boundaries.
Also, THP is only enabled for anonymous memory regions. There are plans to add support for tmpfs and page cache. THP tunables are found in the
/sys
tree under
/sys/kernel/mm/redhat_transparent_hugepage
.
The values for
/sys/kernel/mm/redhat_transparent_hugepage/enabled
can be one of the following:
always - always use THP never - disable THP
khugepaged will be automatically started when transparent_hugepage/enabled is set to "always" or "madvise, and it'll be automatically shutdown if it's set to "never". The redhat_transparent_hugepage/defrag parameter takes the same values and it controls whether the kernel should make aggressive use of memory compaction to make more hugepages available.
Check system-wide THP usage
Run the following command to check system-wide THP usage:
# grep AnonHugePages /proc/meminfo AnonHugePages: 632832 kB
Note: Red Hat Enterprise Linux 6.2 or later publishes additional THP monitoring via
/proc/vmstat
:
# egrep 'trans|thp' /proc/vmstat nr_anon_transparent_hugepages 2018 thp_fault_alloc 7302 thp_fault_fallback 0 thp_collapse_alloc 401 thp_collapse_alloc_failed 0 thp_split 21
Check THP usage per process
Run the following command to monitor which processes are using THP:
# grep -e AnonHugePages /proc/*/smaps | awk '{ if($2>4) print $0} ' | awk -F "/" '{print $0; system("ps -fp " $3)} ' /proc/7519/smaps:AnonHugePages: 305152 kB UID PID PPID C STIME TTY TIME CMD qemu 7519 1 1 08:53 ? 00:00:48 /usr/bin/qemu-system-x86_64 -machine accel=kvm -name rhel7 -S -machine pc-i440fx-1.6,accel=kvm,usb=of /proc/7610/smaps:AnonHugePages: 491520 kB UID PID PPID C STIME TTY TIME CMD qemu 7610 1 2 08:53 ? 00:01:30 /usr/bin/qemu-system-x86_64 -machine accel=kvm -name util6vm -S -machine pc-i440fx-1.6,accel=kvm,usb= /proc/7788/smaps:AnonHugePages: 389120 kB UID PID PPID C STIME TTY TIME CMD qemu 7788 1 1 08:54 ? 00:00:55 /usr/bin/qemu-system-x86_64 -machine accel=kvm -name rhel64eus -S -machine pc-i440fx-1.6,accel=kvm,us
To disable THP at boot time
Append the following to the kernel command line in
grub.conf
:
transparent_hugepage=never
Note: Certain ktune and/or tuned profiles specify to enable THP when they are applied. If the
transparent_hugepage=never
parameter is set at boot time, but THP does not appear to be disabled after the system is fully booted. Refer to the following article:
To disable THP at run time
Run the following commands to disable THP on-the-fly:
# echo never > /sys/kernel/mm/redhat_transparent_hugepage/enabled # echo never > /sys/kernel/mm/redhat_transparent_hugepage/defrag
- NOTE: Running the above commands will stop only creation and usage of the new THP. The THP which were created and used at the moment the above commands were run would not be disassembled into the regular memory pages. To get rid of THP completely the system should be rebooted with THP disabled at boot time.
-
NOTE: Some third party application install scripts check value of above files and complain even if THP is disabled at boot time using
transparent_hugepage=never
, this is due to the fact when THP is disabled at boot time, the value of/sys/kernel/mm/redhat_transparent_hugepage/defrag
will not be changed, however this is expected and system will never go in THP defragmentation code path when it is disabled at boot and THP defrag need not to be disabled separately.
How to tell if Explicit HugePages is enabled or disabled
There can be two types of HugePages in the system: Explicit Huge Pages which are allocated explicitly by
vm.nr_hugepages
sysctl parameter and Transparent Huge Pages which are allocated automatically by the kernel. See below on how to tell if Explicit HugePages is enabled or disabled.
-
Explicit HugePages DISABLED:
-
If the value of
HugePages_Total
is "0" it means HugePages is disabled on the system.# grep -i HugePages_Total /proc/meminfo HugePages_Total: 0
-
Similarly, if the value in
/proc/sys/vm/nr_hugepages
file orvm.nr_hugepages
sysctl parameter is "0" it means HugePages is disabled on the system:# cat /proc/sys/vm/nr_hugepages # sysctl vm.nr_hugepages vm.nr_hugepages = 0
-
-
Explicit HugePages ENABLED:
-
If the value of
HugePages_Total
is greater than "0", it means HugePages is enabled on the system:# grep -i HugePages_Total /proc/meminfo HugePages_Total: 1024
-
Similarly if the value in
/proc/sys/vm/nr_hugepages
file orvm.nr_hugepages
sysctl parameter is greater than "0", it means HugePages is enabled on the system:# cat /proc/sys/vm/nr_hugepages 1024 # sysctl vm.nr_hugepages vm.nr_hugepages = 1024
-
Comments
- RHEL 6 disables THP on systems with < 1G of ram. Refer to Red Hat for more information.
- Disadvantages of using the explicit hugepages (libhugetlbfs): Using hugetlbfs requires significant work from both application developers and system administrators; explicit hugepages must be set aside at boot time, and applications must map them explicitly. The process is fiddly enough that use of hugetlbfs is restricted to those who really care and who have the time to mess with it. Hugetlbfs is often seen as a feature for large, proprietary database management systems and little else.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/31439444/viewspace-2674006/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- oracle之 關閉透明大頁Oracle
- Oracle 標準大頁和透明大頁Oracle
- Apache APISIX透過頁面配置路由ApacheAPI路由
- Red Hat Enterprise Linux 7的新功能Linux
- Red Hat Enterprise LinuxLinux
- 從 Red Hat Enterprise Linux 2.1 AS升級到 Red Hat Enterprise Linux 3Linux
- Red Hat Enterprise Linux 7.4Linux
- Red Hat Enterprise Linux 6官方中文文件Linux
- Web頁面製作基礎Web
- How to disable transparent hugepages (THP) on Red Hat Enterprise Linux 7Linux
- 動態路由,透過id改變,改頁面路由
- 透過結構化資料構建頁面
- JavaScript 倒數計時關閉頁面JavaScript
- 如何透過Python程式碼旋轉PDF頁面Python
- Flutter頁面保活及保持頁面跳轉位置Flutter
- 058、Vue3+TypeScript基礎,頁面通訊之父頁面使用$parent的用法VueTypeScript
- Red Hat Enterprise Linux Server 7.4 安裝LinuxServer
- Red Hat Enterprise Linux 9的簡介Linux
- 如何關閉移動web頁面縮放功能Web
- JS 監聽使用者頁面訪問&頁面關閉並進行資料上報操作JS
- OAF_OAF Framework頁面分析(概念)Framework
- android專案點餐app1:基礎功能:閃屏頁、登入頁面、註冊頁面AndroidAPP
- Red Hat Enterprise Linux 6使用 XDMCP (Xmanager)的一些設定Linux
- Red Hat Enterprise Linux使用資源的限制Linux
- Red Hat Enterprise Linux AS4-U3硬碟Linux硬碟
- 關閉瀏覽器頁面時彈出是否關閉提示框瀏覽器
- 【TUNE_ORACLE】Oracle資料庫與HugePages(四)如何禁用透明大頁Oracle資料庫
- JavaScript 點選頁面其他地方關閉視窗JavaScript
- Selenium常用操作——關閉頁面和瀏覽器瀏覽器
- js關閉當前頁面視窗的問題JS
- web頁面引用相關檔案或者頁面方式彙總Web
- 前端面試7:頁面效能前端面試
- js頁面跳轉的問題(跳轉到父頁面、最外層頁面、本頁面)JS
- vue單頁面應用, 頁面重新整理, 後退, 前進及關閉時, vue執行的生命週期鉤子Vue
- Xamarin.FormsShell基礎教程(6)Shell專案內容詳情頁面ORM
- 不用USB,透過adb無線除錯安卓手機頁面除錯安卓
- 面對四大硬傷 Red Hat 謀變Linux渠道(轉)Linux
- python django整理(三)頁面基礎(仿BBS)PythonDjango