SGA and PGA Advice
- From: Sanjay Mishra <smishra_97@xxxxxxxxx>
- To: "oracle-l@xxxxxxxxxxxxx" <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 18 May 2012 20:12:44 -0700 (PDT)
Hi Experts
Looking for some advice on v$sga_target_advice. I am seeing the following data
from one of my 11g R2 Database. Not using AMM
SGA_SIZE SGA_SIZE_FACTOR ESTD_DB_TIME_FACTOR
---------- --------------- -------------------
1116 .5 1.0030
1604 .75 1.0010
2252 1 1
2820 1.25 .9999
3306 1.5 .9999
3886 1.75 .9999
4456 2 .9999
Now it shows that current setting of sga_target of 2820 can be reduce to 1116
as there is not big benefit from 1116 to 2820 as bot shows ESTD_DB_IME_FACTOR
close to 1. Or if we have to go with 2820. The reason is that there is not high
memory on the system
Similarly v$pga_target_advice
PGA_MB CACHE_HIT ESTD_OVERALLOC_COUNT
---------- ---------- --------------------
110 66 22917
250 66 22112
300 95 0
800 96 0
1100 96 0
1340 96 0
1580 96 0
1800 96 0
2200 96 0
Is that shows thatPGA_AGGREGATE_TARGET of 300M is enought or has to go for 800.
Is 800 is only good value inspite not much cache hit and if provide some reason.
TIA
Sanjay
--
//www.freelists.org/webpage/oracle-l
Other related posts:
- » SGA and PGA Advice - Sanjay Mishra
