http://oracledbasagar.blogspot.de/2012/04/pga-sga-memory-advisors.

html
select sga_size,sga_size_factor,estd_db_time from v$sga_target_advice;
=================================================
select pga_target_for_estimate,pga_target_factor,estd_extra_bytes_rw from v$pga_
target_advice;
Value=1358954496 (for 1) is the current pga_aggregate_target value (set in in
itorcldb.ora)
So, Subtract pga_target_for_estimate - estd_extra_bytes_rw for 5th row , 1358954
496-954314752
equals to 404639744 i.e eqals to 386 MB.
So, conclusion is that adding extra 386 MB will improve performance(less I/O wou
ld be needed).
=================================================
select memory_size,memory_size_factor,estd_db_time from v$memory_target_advice;
=================================================
V$DB_CACHE_ADVISOR
Here is how we query the V$DB_CACHE_ADVISOR in order to see the estimated physic
al reads for different buffer cache size:
SELECT a.size_for_estimate "Buffer size MB",
a.size_factor "Factor size",
round(a.estd_physical_read_time/1000,2) "Estim. time (s)",
a.estd_physical_read_factor "Estim. time factor",
a.estd_physical_reads "Estim. nb physical read"
FROM sys.v$db_cache_advice a
WHERE a.name='DEFAULT'
ORDER BY a.size_for_estimate;
=================================================
V$SYSTAT
I ll display the instance statistics (cumulative since instance startup) that meas
ure physical reads:
SQL> select value,name from v$sysstat where name like 'physical reads %';