RE: ASSM - dynamic memory resizing
- From: "Hameed, Amir" <Amir.Hameed@xxxxxxxxx>
- To: "K Gopalakrishnan" <kaygopal@xxxxxxxxx>
- Date: Fri, 30 Nov 2007 15:20:47 -0500
Gopal,
You are right that we are running Solaris. I just confirmed with our
onsite Sun support person that all the memory resides on the CPU boards.
So, what does the "main memory" category mean here because it seems that
this is the way Oracle kernel is reporting it and has no similarity with
the way the memory is located on the hardware.
-----Original Message-----
From: K Gopalakrishnan [mailto:kaygopal@xxxxxxxxx]
Sent: Friday, November 30, 2007 1:34 PM
To: Hameed, Amir
Cc: Oracle-L Freelists
Subject: Re: ASSM - dynamic memory resizing
Amir,
Do you have any additional information on memory mapping of the 6 boards
and main memory details.. ?
BTW is it Sun Solairs? I guess the locality 0-5 coming from six boards
(NUMA allocation) and 129 is coming from main memory. Check the
following patent
(http://www.patentstorm.us/patents/6021479-claims.html) for some
interesting information for memory allocations on locality domains.
-Gopal
On Nov 30, 2007 11:56 AM, Hameed, Amir <Amir.Hameed@xxxxxxxxx> wrote:
>
> When I run the following statement, I see the result as shown below:
> select LOCALITY, sum(GRANSIZE) gransize from sys.x$ksmge group by
> LOCALITY ;
>
> LOCALITY SUM_GRANSIZE
> ---------- ---------------
> 129 3,254,779,904
> 5 2,130,706,432
> 1 2,147,483,648
> 2 2,130,706,432
> 3 2,130,706,432
> 0 2,147,483,648
> 4 2,130,706,432
> ---------------
> sum 16,072,572,928
>
> I understand that numbers 0-5 refer to the memory boards on the
system.
> In my case there are six boards (24 dual-core CPUs) and each board has
> memory on it. What does number 129 refer to?
>
>
> -----Original Message-----
> From: Taylor, Chris David [mailto:Chris.Taylor@xxxxxxxxxxxxxxx]
> Sent: Friday, November 30, 2007 11:53 AM
> To: kaygopal@xxxxxxxxx; Hameed, Amir
> Cc: Oracle-L Freelists
>
> Subject: RE: ASSM - dynamic memory resizing
>
> Personally, I love it when ASSM forces the shared pool to 3x the size
> of the buffer cache, by taking memory _away_ from the buffer cache.
>
> That's fantastic. Gotta love it.
>
> I know, I know. "Bind Variables". Tell that to PeopleSoft who is
> Oracle
> :)
>
>
> Chris Taylor
> Sr. Oracle DBA
> Ingram Barge Company
> Nashville, TN 37205
> Office: 615-517-3355
> Cell: 615-354-4799
> Email: chris.taylor@xxxxxxxxxxxxxxx
>
> -----Original Message-----
> From: oracle-l-bounce@xxxxxxxxxxxxx
> [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of K Gopalakrishnan
> Sent: Friday, November 30, 2007 10:47 AM
> To: Amir.Hameed@xxxxxxxxx
> Cc: Oracle-L Freelists
> Subject: Re: ASSM - dynamic memory resizing
>
> Amir,
>
> The frequency depends on the memory pressure. I am not aware whether
> there are any fixed intervals , where MMAN checks the memory
> allocations. However you can trace the operations using
> "_memory_management_tracing".
>
> -Gopal
>
>
> On Nov 30, 2007 8:50 AM, Hameed, Amir <Amir.Hameed@xxxxxxxxx> wrote:
> > Folks,
> > Does anyone know what process does the dynamic memory resizing when
> ASSM
> > is enabled? Also, what is the frequency of this operation or is it
> > triggered by some event? From the v$sga_dynamic
> > _components.last_oper_time, this does not seem to be triggered at
> fixed
> > time intervals.
> >
> > Thanks
> > Amir
> >
> > --
> > //www.freelists.org/webpage/oracle-l
> >
> >
> >
>
>
>
> --
> Best Regards,
> K Gopalakrishnan
> Co-Author: Oracle Wait Interface, Oracle Press 2004
> http://www.amazon.com/exec/obidos/tg/detail/-/007222729X/
>
> Author: Oracle Database 10g RAC Handbook, Oracle Press 2006
> http://www.amazon.com/gp/product/007146509X/
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
>
>
--
Best Regards,
K Gopalakrishnan
Co-Author: Oracle Wait Interface, Oracle Press 2004
http://www.amazon.com/exec/obidos/tg/detail/-/007222729X/
Author: Oracle Database 10g RAC Handbook, Oracle Press 2006
http://www.amazon.com/gp/product/007146509X/
--
//www.freelists.org/webpage/oracle-l
Other related posts: