转载请注明出处:https://blog.csdn.net/guoyjoe/article/details/17138391
什么时侯使用大页呢,当你主机的物理内存为64G,设SGA>=32G时,建议开启大页,步骤如下:
1、 关闭Oracle Database 11g中的AMM(Automatic Memory Management),即把两个参数MEMORY_TARGET / MEMORY_MAX_TARGET设为0
如果设考数 MEMORY_MAX_TARGET为0不成功,那么请考参https://blog.csdn.net/guoyjoe/article/details/12845965
gyj@OCM> show parameter memory_max_target
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
memory_max_target big integer 0
gyj@OCM> show parameter memory_target
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
memory_target big integer 0
2、参考metalink(文档 ID 401749.1)提供的脚本,计算hugepages的大小
#!/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
# https://support.oracle.com
# Welcome text
echo "
This script is provided by Doc ID 401749.1 from My Oracle Support
(https://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" ;;
esac
# End
[oracle@mydb admin]$ chmod +x hugepages_settings.sh
This script is provided by Doc ID 401749.1 from My Oracle Support
(https://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...
Recommended setting: vm.nr_hugepages = 1028
gyj@OCM> show parameter sga_max_size
5、设置hugepages,在内核参数中添加一行,vi /etc/sysctl.conf
vm.nr_hugepages = 1028
6、修改内核参数立即生效
net.ipv4.ip_forward = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
kernel.sysrq = 0
kernel.core_uses_pid = 1
net.ipv4.tcp_syncookies = 1
kernel.msgmnb = 65536
kernel.msgmax = 65536
kernel.shmmax = 68719476736
kernel.shmall = 4294967296
fs.file-max = 6815744
vm.nr_hugepages = 1028
[root@mydb ~]# vi /etc/security/limits.conf
oracle soft memlock 2056000
8、检查limits是否正确
9、重启数据库—注原来的orale用户的窗口退到root用户,重新su – oracle
sys@OCM> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
[oracle@mydb ~]$ exit
logout
You have new mail in /var/spool/mail/root
[root@mydb ~]# su - oracle
[oracle@mydb ~]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.3.0 Production on Thu Dec 5 10:56:20 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
sys@OCM> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
sys@OCM> startup
ORACLE instance started.
Total System Global Area 2137886720 bytes
Fixed Size 2230072 bytes
Variable Size 1409288392 bytes
Database Buffers 603979776 bytes
Redo Buffers 122388480 bytes
Database mounted.
Database opened.
[oracle@mydb ~]$ watch -n1 ‘cat /proc/meminfo |grep -i HugePage’
Every 1.0s: cat /proc/meminfo |grep -i HugePage Thu Dec 5 11:09:06 2013
HugePages_Total: 1028
HugePages_Free: 869
HugePages_Rsvd: 842
Hugepagesize: 2048 kB
系统承诺给Oracle预留842页,即842*2M=1684M(1684+118==SGA_MAX_SIZE)
sys@OCM> alter system set pre_page_sga=true scope=spfile;
System altered.
sys@OCM> show parameter sga
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
lock_sga boolean FALSE
pre_page_sga boolean TRUE
sga_max_size big integer 2G
sga_target big integer 1G
For 11.2.0.2 and further, the Oracle Database Server has added a new parameter that helps managing the hugepages for use by the database.
补充关于内存申请的OverCommit:
Linux下的OverCommit机制,主要是为了应对可能的异常的大量内存申请对OS本身造成冲击。
[root@mydb vm]# cd /proc/sys/vm
[root@mydb vm]# ls
block_dump flush_mmap_pages min_free_kbytes overcommit_memory swappiness
dirty_background_ratio hugetlb_shm_group min_slab_ratio overcommit_ratio swap_token_timeout
dirty_expire_centisecs laptop_mode min_unmapped_ratio pagecache vfs_cache_pressure
dirty_ratio legacy_va_layout mmap_min_addr page-cluster zone_reclaim_mode
dirty_writeback_centisecs lowmem_reserve_ratio nr_hugepages panic_on_oom
drop_caches max_map_count nr_pdflush_threads percpu_pagelist_fraction
假设操作系统只有1000M内存,有个应用请求操作系统需要1200M内存,操作系统会承诺给1200M,即由OverCommit承诺,这时还没有真正分配空间。