RE: RAC install on Linux

From: Ruel, Chris <>
Date: Thu, 22 Feb 2018 20:37:01 +0000
Message-ID: <>

Someone correct me if I am wrong but HP's do not lock memory. They just use a larger page size. In fact some people had problems locking memory with HP's enabled. I don't know if Oracle ever admitted to this being a bug. This note is a little older but I know it affected us as late as

Oracle Support Document 1276966.1 (Rac Nodes Frequently Evicted (Rebooted) By CRS When PRE_PAGE_SGA is Set to True) can be found at:

Also, looking at the thread below, this is news to me that you must use ASMM with HP's. We use HP's with standard memory management in some cases and it seems to work fine. I know that AMM is a no-no.


Chris Ruel * Oracle Database Administrator * Lincoln Financial Group * Desk:317.759.2172 * Cell 317.523.8482

-----Original Message-----
From: [] On Behalf Of Hameed, Amir Sent: Thursday, February 22, 2018 3:06 PM To:; Cc: Oracle-L Freelists <> Subject: RE: RAC install on Linux

***This email is from an external source. Only open links and attachments from a Trusted Sender.***

In those VM shops where memory is over-subscribed, how do Huge Pages work in terms of locking memory pages so that they cannot be swapped?

-----Original Message-----
From: [] On Behalf Of Stefan Koehler Sent: Thursday, February 22, 2018 5:21 AM To:
Cc: Oracle-L Freelists <> Subject: Re: RAC install on Linux

Hello Neil,

> You also have contiguous memory allocation and it can’t be swapped.

Hugepages can also be non-contiguous aka. fragmented - called external fragmentation ( AFAIK this is also the reason why Oracle has implemented enhancement request #14500387 and you get an "ORA-27107: AUTO value for USE_LARGE_PAGES parameter is no longer supported" ( nowadays for dynamic huge pages allocation via oradism.

Best Regards
Stefan Koehler

Independent Oracle performance consultant and researcher Website:
Twitter: _at_OracleSK

> Neil Chandler <> hat am 22. Februar 2018 um 09:47 geschrieben:
> Transparent Hugepages should be disabled, to prevent the Kernel “helping you out” and causing CPU spikes and unpredictable performance hits.
> You should always be using Hugepages.
> They give a minor performance improvement and a significant memory saving in terms of the amount of memory needed to handle the pages - less Transaction Lookaside Buffers, which also means less TLB misses (which are expensive).
> You are handling the memory chopped up into 2MB pieces instead of 4K. But you also have a single shared memory TLB for Hugepages.
> The kernel has less work to do, bookkeeping fewer pointers in the TLB.
> You also have contiguous memory allocation and it can’t be swapped.
> If you are having problems with Hugepages, you have probably overallocated them (I’ve seen this several times at clients so it’s not uncommon). Hugepages can *only* by used for your SGA’s. All of your SGA’s should fit into the Hugepages and that should generally be no more than about 60% of the total server memory (but there are exceptions), leaving plenty of “normal” memory (small pages) for PGA , O/S and other stuff like monitoring agendas.
> As an added bonus, AMM can’t use Hugepages, so your are forced to use ASMM. AMM doesn’t work well and has been kind-of deprecated by oracle anyway - dbca won’t let you setup AMM if the server has more than 4GB of memory.
> Neil.
> sent from my phone

!��� 0~���+-����
Notice of Confidentiality: **This E-mail and any of its attachments may contain Lincoln National Corporation proprietary information, which is privileged, confidential, or subject to copyright belonging to the Lincoln National Corporation family of companies. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. Thank You.**
i0zX+n{+i^ Received on Thu Feb 22 2018 - 21:37:01 CET

Original text of this message