Linux之HugePages快速配置

2023-10-10 17:53:33 浏览数 (1)

关于Linux系统的HugePages与Oracle数据库优化，可以参考熊爷之前的文章，相关概念介绍的非常清晰：

  • Linux大内存页Oracle数据库优化

本文旨在Linux系统上快速配置HugePages：

  • 1.设置memlock无限制
  • 2.设置合理的vm.nr_hugepages
  • 3.确认HugePages设置成功

测试环境：RHEL6.8 512G物理内存；Oracle 11.2.0.4 SGA=400G.

1.设置memlock无限制

在/etc/security/limits.conf配置文件中，设置oracle用户memlock无限制： vi /etc/security/limits.conf

代码语言：javascript复制
oracle soft memlock unlimited
oracle hard memlock unlimited

2.设置合理的vm.nr_hugepages

在/etc/sysctl.conf配置文件中，设置合理的vm.nr_hugepages值。 运行MOS 401749.1提供的hugepages_settings.sh脚本，直接可以得到建议值。 hugepages_settings.sh脚本内容，若和MOS有区别，以MOS最新版本为准：

代码语言：javascript复制
#!/bin/bash
#
# hugepages_settings.sh
#
# Linux bash script to compute values for the
# recommended HugePages/HugeTLB configuration
# on Oracle Linux
#
# Note: This script does calculation for all shared memory
# segments available when the script is run, no matter it
# is an Oracle RDBMS shared memory segment or not.
#
# This script is provided by Doc ID 401749.1 from My Oracle Support
# http://support.oracle.com

# Welcome text
echo "
This script is provided by Doc ID 401749.1 from My Oracle Support
(http://support.oracle.com) where it is intended to compute values for
the recommended HugePages/HugeTLB configuration for the current shared
memory segments on Oracle Linux. Before proceeding with the execution please note following:
 * For ASM instance, it needs to configure ASMM instead of AMM.
 * The 'pga_aggregate_target' is outside the SGA and
   you should accommodate this while calculating the overall size.
 * In case you changes the DB SGA size,
   as the new SGA will not fit in the previous HugePages configuration,
   it had better disable the whole HugePages,
   start the DB with new SGA size and run the script again.
And make sure that:
 * Oracle Database instance(s) are up and running
 * Oracle Database 11g Automatic Memory Management (AMM) is not setup
   (See Doc ID 749851.1)
 * The shared memory segments can be listed by command:
     # ipcs -m


Press Enter to proceed..."

read

# Check for the kernel version
KERN=`uname -r | awk -F. '{ printf("%d.%dn",$1,$2); }'`

# Find out the HugePage size
HPG_SZ=`grep Hugepagesize /proc/meminfo | awk '{print $2}'`
if [ -z "$HPG_SZ" ];then
    echo "The hugepages may not be supported in the system where the script is being executed."
    exit 1
fi

# Initialize the counter
NUM_PG=0

# Cumulative number of pages required to handle the running shared memory segments
for SEG_BYTES in `ipcs -m | cut -c44-300 | awk '{print $1}' | grep "[0-9][0-9]*"`
do
    MIN_PG=`echo "$SEG_BYTES/($HPG_SZ*1024)" | bc -q`
    if [ $MIN_PG -gt 0 ]; then
        NUM_PG=`echo "$NUM_PG $MIN_PG 1" | bc -q`
    fi
done

RES_BYTES=`echo "$NUM_PG * $HPG_SZ * 1024" | bc -q`

# An SGA less than 100MB does not make sense
# Bail out if that is the case
if [ $RES_BYTES -lt 100000000 ]; then
    echo "***********"
    echo "** ERROR **"
    echo "***********"
    echo "Sorry! There are not enough total of shared memory segments allocated for
HugePages configuration. HugePages can only be used for shared memory segments
that you can list by command:

    # ipcs -m

of a size that can match an Oracle Database SGA. Please make sure that:
 * Oracle Database instance is up and running
 * Oracle Database 11g Automatic Memory Management (AMM) is not configured"
    exit 1
fi

# Finish with results
case $KERN in
    '2.4') HUGETLB_POOL=`echo "$NUM_PG*$HPG_SZ/1024" | bc -q`;
           echo "Recommended setting: vm.hugetlb_pool = $HUGETLB_POOL" ;;
    '2.6') echo "Recommended setting: vm.nr_hugepages = $NUM_PG" ;;
    '3.8') echo "Recommended setting: vm.nr_hugepages = $NUM_PG" ;;
    '3.10') echo "Recommended setting: vm.nr_hugepages = $NUM_PG" ;;
    '4.1') echo "Recommended setting: vm.nr_hugepages = $NUM_PG" ;;
    '4.14') echo "Recommended setting: vm.nr_hugepages = $NUM_PG" ;;
    '4.18') echo "Recommended setting: vm.nr_hugepages = $NUM_PG" ;;
    '5.4') echo "Recommended setting: vm.nr_hugepages = $NUM_PG" ;;
    *) echo "Kernel version $KERN is not supported by this script (yet). Exiting." ;;
esac

# End

直接运行脚本即可得到对应的建议：

代码语言：javascript复制
--当启动的实例设置SGA_MAX_SIZE=12G，给出建议：
Recommended setting: vm.nr_hugepages = 6148

--当启动的实例设置SGA_MAX_SIZE=400G，给出建议：
Recommended setting: vm.nr_hugepages = 204805

--当没有启动实例时，会报错提示：
***********
** ERROR **
***********
Sorry! There are not enough total of shared memory segments allocated for 
HugePages configuration. HugePages can only be used for shared memory segments 
that you can list by command:

    # ipcs -m

of a size that can match an Oracle Database SGA. Please make sure that:
 * Oracle Database instance is up and running 
 * Oracle Database 11g Automatic Memory Management (AMM) is not configured

我这里将建议值vm.nr_hugepages = 204805追加到/etc/sysctl.conf配置文件中，然后执行sysctl -p生效配置。

3.确认HugePages设置成功

查看关于HugePages的信息，注意HugePages_Total值是之前设置的204805： grep Huge /proc/meminfo

代码语言：javascript复制
# grep Huge /proc/meminfo 
AnonHugePages:         0 kB
HugePages_Total:   204805
HugePages_Free:    168475
HugePages_Rsvd:    168471
HugePages_Surp:        0
Hugepagesize:       2048 kB

数据库在启动时，对应alert日志中会有“Large Pages Information”内容：

代码语言：javascript复制
Wed Nov 14 14:38:12 2018
Starting ORACLE instance (normal)
************************ Large Pages Information *******************
Per process system memlock (soft) limit = UNLIMITED
 
Total Shared Global Region in Large Pages = 400 GB (100%)
 
Large Pages used by this instance: 204801 (400 GB)
Large Pages unused system wide = 4 (8192 KB)
Large Pages configured system wide = 204805 (400 GB)
Large Page size = 2048 KB
********************************************************************

至此可以确认HugePages设置成功。

linux 脚本 内存 配置 系统

0 人点赞