Huge Pages in Oracle

HugePages is a feature integrated into the Linux kernel from Release 2.6 that allows large SGA memory to be utilized with reduced overhead by ensuring that the memory is not paged to disk. HugePages allows you to use much larger page sizes (for example, 2MB or 4MB) than the default 4K page size, which can be crucial for faster Oracle database performance on Linux, and increasingly so for systems with large RAM and database SGA sizes, as is the case even for small CC deployments.
 
HugePages results in smaller page tables and less CPU time spent on memory management, increasing the performance of large database instances
 
One possible drawback of using HugePages is that you cannot use it in conjunction with Automatic Memory Management (AMM); you must use Automatic Shared Memory Management (ASMM) instead. Therefore, before you decide to implement HugePages, you may want to weigh its advantages against any disadvantages of not being able to enable AMM.

Without HugePages, the operating system keeps each 4KB of memory as a page, and when it is allocated to the SGA, then the lifecycle of that page (dirty, free, mapped to a process, and so on) is kept up to date by the operating system kernel.

With HugePages, the operating system page table (virtual memory to physical memory mapping) is smaller, since each page table entry is pointing to pages from 2MB to 256MB. Also, the kernel has fewer pages whose lifecyle must be monitored.

You cannot use Automatic Memory Management (AMM) while implementing HugePages, because AMM works on dynamic SGA and PGA tuning. For example AMM can unmap the unused SGA space and map it to PGA and back. With HugePages contiguous pages are preallocated and cannot be used for anything else but for System V shared memory (for example, SGA).

When you use AMM, the entire SGA memory is allocated by creating files under /dev/shm. When Oracle Database allocates SGA with AMM, HugePages are not reserved. To use HugePages you must disable AMM.

 Oracle Metadata Link  https://www.oracle.com/ca-en/technical-resources/articles/it-infrastructure/dev-hugepages.html 

 

Aws Metadata Link : https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Oracle.Concepts.HugePages.html

Comments

Post a Comment

Popular posts from this blog

FRA Usage and Administration

Image
 In Oracle database, the Flash Recovery Area or FRA is a location on disk where the database can create and manage several kinds of backup and recovery-related files. Main file types are archivelog, flashback log, backups, as well as mirrors for your control files and redo log files. All files in the FRA are Oracle-managed files. Using a Flash Recovery Area simplifies the administration of your database by automatically retaining them for as long as they are needed for restore and recovery activities, and deleting them when they are no longer needed, because the space is needed for another backup and recovery-related purpose. Checking the current usage  You can check the configuration by looking at two parameters.The parameters are db_receovery_file_dest and second one db_recovery_file_dest_size .  db_receovery_file_dest point to location where the files will be located in Server . FOr normal single Databases this will be any directory for RAC this will b...
Read more

Oracle Architecture SGA

Image
 Architecture :   Basic Memory Structures Oracle Database includes several memory areas, each of which contains multiple subcomponents. The basic memory structures associated with Oracle Database include: ·          System global area (SGA) The SGA is a group of shared memory structures, known as SGA components , that contain data and control information for one Oracle Database instance. All server and background processes share the SGA. Examples of data stored in the SGA include cached data blocks and shared SQL areas. ·          Program global area (PGA) A PGA is a nonshared memory region that contains data and control information exclusively for use by an Oracle process. Oracle Database creates the PGA when an Oracle process starts.One PGA exists for each server process and background process. The collection of individual PGAs is the total instance PGA, or instance PGA . Database ...
Read more

Cold Backup Cloning of Database .

 Cold Backup :  A cold backup is done when there is no user activity going on with the system. Also called as offline backup, is taken when the database is not running and no users are logged in. all files of the database are copied and no changes during the copy are made. Cold backup can be preformed when Database is in archive mode as well as Non archive log mode  . Backup Strategy :  Gather all the details of physical files (CRD) files in  database . redo log files are online redo log and archived redo log ones .   Select file_name,tablespace_name from dba_data_files  ; select * from v$controlfile  select member from v$logfile ; select name from v$archived_Log ;  create pfile from spfile  Backup  the contol file manually . alter database backup controlfile to trace as '/tmp/coldbackup_controlfile.sql' ;     Stop all the DB services (Database ,Listener)on source DB Server. Copy all the files(Datafiles,redo...
Read more