![]() It is typically the combination of a large SGA and lots database connections that leads to problems. Just because you have a large SGA, it doesn't automatically mean you will have a problem if you don't use HugePages. The savings in memory and the effort of page management make HugePages pretty much mandatory for Oracle 11g systems running on x86-64 architectures. In addition to these changes, the memory associated with HugePages can not be swapped out, which forces the SGA to stay memory resident. ![]() Using HugePages, the page size is increased to 2MB (configurable to 1G if supported by the hardware), thereby reducing the total number of pages to be managed by the kernel and therefore reducing the amount of memory required to hold the page table in memory. Without HugePages, the memory of the SGA is divided into 4K pages, which have to be managed by the Linux kernel. Disabling Transparent HugePages (RHEL6/OL6 and RHEL7/OL7)įor large SGA sizes, HugePages can give substantial benefits in virtual memory management.Force Oracle to use HugePages (USE_LARGE_PAGES).Home » Articles » Linux » Here Configuring HugePages for Oracle on Linux (x86-64)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |