RE: Prevent ASM from using any hugepages

  • From: "Bobak, Mark" <Mark.Bobak@xxxxxxxxxxxx>
  • To: Oleksandr Denysenko <odenysenko@xxxxxxxxx>
  • Date: Fri, 17 May 2013 19:48:54 +0000

Yeah, sorry, Chris pointed that out.  I've been away from 10g for quite a while 
From: Oleksandr Denysenko [mailto:odenysenko@xxxxxxxxx]
Sent: Friday, May 17, 2013 3:43 PM
To: Bobak, Mark
Cc: ora_kclosson@xxxxxxxxx; oracle-l@xxxxxxxxxxxxx; 
Subject: RE: Prevent ASM from using any hugepages


It's 10.2 so no AMM...

Oleksandr Denysenko

17.05.2013 22:39 ÐÏÌØÚÏ×ÁÔÅÌØ "Bobak, Mark" 
<Mark.Bobak@xxxxxxxxxxxx<mailto:Mark.Bobak@xxxxxxxxxxxx>> ÎÁÐÉÓÁÌ:
> Chris,
> Just use AMM (MEMORY_TARGET) for ASM, and it *can't* use hugepages.  That's 
> the default set up, anyhow.  So, just install ASM and forget it, and it won't 
> touch any hugepages.
> That's how I have all my boxes set up.
> I have to add:
> Just got back from GLOC, had some discussions about hugepages with a few 
> folks.  Still surprises me how many people don't bother with hugepages!
> My three rules about hugepages are as follows:
> 1.)  If you're not using hugepages, you're doing it wrong.  Period.  (Yes, 
> ok, for very tiny databases and low loads, it may not be worth the time.  
> But, what if that database gets busier over time?  Just get used to doing it 
> on all your databases.)
> 2.)  #1 doesn't apply to ASM instances.
> 3.) 'alter system set use_large_pages = ONLY;' is your friend.
> -Mark


Other related posts: