RE: Linux- AMM, ASMM, Hugepages , swappiness
- From: D'Hooge Freek <Freek.DHooge@xxxxxxxxx>
- To: "vishal@xxxxxxxxxxxxxxx" <vishal@xxxxxxxxxxxxxxx>, "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 9 Nov 2009 16:20:04 +0100
Vishal,
Kevin Closson has written a blog post about it:
http://kevinclosson.wordpress.com/2007/08/23/oracle11g-automatic-memory-management-and-linux-hugepages-support/
Regards,
Freek D'Hooge
Uptime
Oracle Database Administrator
email: freek.dhooge@xxxxxxxxx
tel +32(0)3 451 23 82
http://www.uptime.be
disclaimer: www.uptime.be/disclaimer
________________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Vishal Gupta
Sent: maandag 9 november 2009 15:45
To: oracle-l@xxxxxxxxxxxxx
Subject: Linux- AMM, ASMM, Hugepages , swappiness
Hello List,
As we all know, AMM (Automatic Memory Management) feature of 11g is not
compatible with use of HugePages on Linux. One could still use HugePages on
Linux with 11g by disabling AMM, and enabling ASMM (Automatic Shared Memory
Management) and automatic PGA memory management.
AMM is supported using tmpfs on /dev/shm. AMM is not compatible with ramfs on
/dev/shm.
I would have thought that using hugepages has advantages over use of tmpfs on
/dev/shm. As with hugepages, kernel has fewer PTE (page table entry) to
maintain. And hugepage locked memory is locked into physical RAM and is never
swapped to swap filesystem. So your SGA is never swapped during inactive
period, thereby allowing quick ramp up due to sudden activity after a quiet
period.
If using AMM, one can disable swap on Linux using following setting , which
favours pages to be in RAM rather than swap file.
vm.swappiness = 0
Does anyone has any thoughts on which is better to use - (AMM with tmpfs +
vm.swappiness=0 ) or (hugepages + ASMM + automatic PGA) ?
Regards,
Vishal Gupta
http://www.vishalgupta.com ;
--
//www.freelists.org/webpage/oracle-l
Other related posts:
