CConfiguring Large Memory Optimization
This appendix provides information for configuring memory optimization with large page tables on the Linux operating system, using Hugepages. It contains the following topics:
C.1Overview of HugePages
You can choose to configure HugePages. For some uses, HugePages can provide enhanced performance. However, this feature is an advanced configuration option. It is not a requirement for Oracle RAC.
The following is an overview of HugePages. It does not provide RPM or configuration information. The tasks you must perform for configuration depend on kernel distribution and hardware on your system. If you decide to configure your cluster nodes to use
HugePages, then refer to your distribution documentation and to Oracle Technical Network (OTN) and My Oracle Support for further information.
C.1.1What HugePages Provides
HugePages is a feature integrated into the Linux kernel with release 2.6. It is a method to have larger pages where it is useful for working with very large memory. It can be useful for both 32-bit and 64-bit configurations. HugePage sizes vary from 2MB
to 256MB, depending on the kernel version and the hardware architecture. For Oracle Databases, using HugePages reduces the operating system maintenance of page states, and increases TLB (Translation Lookaside Buffer) hit ratio.
Without HugePages, the operating system keeps each 4 KB 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) must be 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 2 MB to 256 MB. Also, the kernel has fewer pages whose lifecyle must be monitored.
For example, if you use HugePages with 64-bit hardware, and you want to map 256 MB of memory, you may need one page table entry (PTE). If you do not use HugePages, and you want to map 256 MB of memory, then you must have 256 MB * 1024 KB/4 KB = 65536 PTEs.
C.2Restrictions for HugePage Configurations
To use HugePages, you must configure Grub to allocate memory for HugePages during system startup. After paging space is reserved, HugePages can be used as needed. However, if the space they require is not reserved in memory during system startup, then a
HugePages allocation may fail.
HugePages are not subject to allocation or release after system startup, unless a system administrator changes the hugepages configuration by modifying the number of pages available, or the pool size.
分享到:
相关推荐
DOS XMS library is a DOS real mode and large memory model C library. Because DOS is ran under real mode, programmer only can access RAM under 1MB. The memory user can use are 640 KB, Other 384 KB are ...
Host aggregates are also used with pre-determined metadata attributes to serve complex scheduling not only based on CPU, Memory, Disk, but also filters like self-developed anti-Affinity on anti-...
memory, and hardware with MS-DOS 5.0. It also contains updates to the User's Guide and Reference. For information about using applications with MS-DOS 5.0, see the APPNOTE.TXT file. 2. SOLVING ...
- Update config.guess/config.sub scripts to May 2010 revisions. - Update Visual Studio 2008 project files in build/win32/vs2008ex-workspace.zip - Added Bochs compilation timestamp after Bochs ...
esp8266 语音播放 //Priorities of the reader and the decoder thread. Higher = higher prio. #define PRIO_READER 11 #define PRIO_MAD 1 //The mp3 read buffer size. 2106 bytes should be enough for up ...
as you can delete unwanted large attachments that take too much disk space in your mailbox. You can also save the list of attachments into xml/html/text/csv file. System Requirements ==============...
- Minor change to the 2D memory test when run with the 3D test (multiple large windows) and the RAM test. Aimed at correcting sympton: Access Violation 0x00404CF9. - Corrections to the mapping of ...
CTOPAS CFG - Config file for Pascal - Turbo C++ interface demo CTOPAS PRJ - Project file for Turbo Pascal - Turbo C++ interface demo DCOPY CPP - C++ example file DEF CPP - C++ example module used ...
- Passing of invalid OPC Item IDs caused a memory leak of the driver's global memory. After the global memory was exhausted, the driver crashed. - Writing of string values failed when using ...
GPEs, to be used for debugging systems with a large number of ACPI interrupts. Implemented support for the "DMAR" ACPI table (DMA Redirection Table) in both the ACPICA headers and the disassembler. ...
o Because of the limited memory available in the Tiny model, it no longer supports graphics functions. o The Version 1.5 graphics drivers (*.BGI) are not compatible with the Version 2.01 graphics...
o Because of the limited memory available in the Tiny model, it no longer supports graphics functions. o The Version 1.5 graphics drivers (*.BGI) are not compatible with the Version 2.0 graphics ...
Because of the GDDR5X memory, which can't be fully utilized for ETH mining (yet). 3. Are AMD cards also affected by slowdowns with increasing DAG size? Only GCN 1.0 GPUs (78x0, 79x0, 270, 280), ...
This makes it easy to use the tools on machines with limited memory (but enough disk space) as well as computer clusters (from a terminal). In addition, the interactive tools can optionally write the...
\$(Config) Release / Debug | \$(Platform) Win32 / Win64 / OSX32 | \<delphi_version> D7..XE8, 10 Seattle includes .dcu and .dfm files for Delphi and .obj and .hpp files for C++ Builder .\Samples...