Re: AW: SGA_MAX_SIZE vs. SGA_TARGET

From: Neil Chandler <neil_chandler_at_hotmail.com>
Date: Mon, 7 Sep 2015 15:11:28 +0100
Message-ID: <DUB404-EAS64588689FEBCA5B9C47E4D85540_at_phx.gbl>



AIX is flexible if you are using "medium" (64k) pages but not if you are using pinned 16m large pages.

I've not had any opportunity to compare the performance of each method, so I can't say which is best under what scenario. Not worked on AIX for 3 years or so.

Neil.
sent from my phone

> On 7 Sep 2015, at 12:45, Zwettler Markus (OIZ) <Markus.Zwettler_at_zuerich.ch> wrote:
>
> AIX is flexible.
>
>
> google “developerworks aix sga_max_size” + see “AIX Performance: Configuration & Tuning for Oracle & Oracle RAC”, Page 24.
>
>
> Cheers, Markus
>
>
>
> Von: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] Im Auftrag von Cee Pee
> Gesendet: Samstag, 5. September 2015 21:21
> An: frits.hoogland_at_gmail.com
> Cc: oracledbaquestions_at_gmail.com; ORACLE-L
> Betreff: Re: SGA_MAX_SIZE vs. SGA_TARGET
>
> How does that work in AIX? If SGA_MAX_SIZE is set at 20G and SGA_TARGET is 10G, does it allocate 10G and let it go up and down, up to a maximum of 20G?
>
> Also if SGA_TARGET and SGA_MAX_SIZE are same, lets say 5Gb, then does oracle guarantee SGA will not take more than 5Gb any time.
>
>
>
> On Sat, Sep 5, 2015 at 1:30 PM, <frits.hoogland_at_gmail.com> wrote:
>
>
> Verstuurd vanaf mijn iPad
>
> Op 5 sep. 2015 om 20:07 heeft Dba DBA <oracledbaquestions_at_gmail.com> het volgende geschreven:
>
> Was really getting worried I was senile and was going to start drooling on myself. I knew I was able to get memory to allocate and deallocate in the past. It was on Solaris.
>
> Does anyone know why this varies by unix/linux flavor? What is solaris doing that Linux does not?
> Every Unix like platform oracle is on has a HP implementation. Because the implementation is depended on cpu huge page support and the implementation in the operating system, you will see changes in how oracle is able to use it, because it is depended on them.
>
> On Solaris (only I believe) PGA can be allocated in HP.
>
>
> On Sat, Sep 5, 2015 at 1:54 PM, Neil Chandler <neil_chandler_at_hotmail.com> wrote:
> It depends upon your platform. Most platforms allocate max_size so having a lower sga_target is pointless and a waste of memory. Some platforms do not (Solaris), and only allocate sga_target, with max_size an unused top limit.
>
> Neil.
> sent from my phone
>
> > On 5 Sep 2015, at 18:51, Dba DBA <oracledbaquestions_at_gmail.com> wrote:
> >
> > yeah this is old. I know its on the web. However, the responses I see are not to the question I have.
> >
> > What is the point to having two parameters? If SGA_MAX_SIZE reserves memory for oracle as an upper bound, but would I want to be able to raise and lower SGA_TARGET? What do I do with the 'spare memory'. PGA_AGGREGATE_TARGET is separate and not taken from memory reserved with SGA_MAX_SIZE
> >
> > db_cache,shared_pool, large_pool,streams, java, etc... all come out of SGA_TARGET. So what is the point to this? I am missing something.
> >
> > I have I have 20 GB SGA_MAX_SIZE and a 10 GB SGA_TARGET. What is oracle doing with the other 10 GB?
> >
>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Mon Sep 07 2015 - 16:11:28 CEST

Original text of this message