有时候在Linux上使用Oracle的时候,为了提高性能,往往会配置HugePages。这里仅说明如何配置HugePages,至于对HugePages的用处和为什么需要配置有兴趣的同学可以参考MOS:HugePages on Linux: What It Is… and What It Is Not… (文档 ID 361323.1)
配置步骤如下:
1、编辑/etc/security/limits.conf文件并设置menlock。memlock是以kb为单位,设置的值一般小于安装的内存。例如,在安装时使用64GB 内存,增加以下语句锁定最大内存限制:
oracle soft memlock 60397977 oracle hard memlock 60397977
2、重新登陆oracle用户并运行以下语句验证memlock设置:
$ ulimit -l 60397977
运行以下命令显示Hugepagesize 值:
grep Hugepagesize /proc/meminfo
3、如果你使用的是Oracle 11g或之后的版本,默认在建库时是采用Automatic Memory Management(AMM)特性,这是和HugePages冲突的,如果需要使用HugePages,则必须先禁用AMM。设置参数MEMORY_TARGET和MEMORY_MAX_TARGET为0。
4、确保所有数据库实例(包含ASM实例)都已经是开启,使用下述脚本计算当前共享内存段hugepages推荐值:
创建脚本hugepages_settings.sh
脚本内容如下:
#!/bin/bash # # hugepages_settings.sh # # Linux bash script to compute values for the # recommended HugePages/HugeTLB configuration # # 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. 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 SGA 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.%d\n",$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.2') echo "Kernel version $KERN is not supported. Exiting." ;; '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" ;; esac # End
授权脚本运行: $ chmod +x hugepages_settings.sh 运行脚本: $ ./hugepages_settings.sh
输出结果:
For 2.4 kernel systems:
$ ./hugepages_settings.sh ... Recommended setting: vm.hugetlb_pool = 78
For 2.6 and 3.8(UEK3) kernel systems:
$ ./hugepages_settings.sh ... Recommended setting: vm.nr_hugepages = 67
5、修改内核参数
编辑/etc/sysctl.conf,设置vm.nr_hugepages参数:
vm.nr_hugepages=78
6、关闭数据库实例并重启服务器
大师文章写的非常详细,谢谢分享