v$sga_resize_ops

 
Hi,

In one of our 10.2.0.4 database, within 5 hours of operation, we saw about 80 RESIZE operations within SGA as below
The SGA_TARGET and SGA_MAX_SIZE are both 1824M

From a best practices / performance perspective, is 80 a high number for re-size operations for buffer cache and shared pool
Based on the output below, what would you recommend?



COMPONENT                 OPER_TYPE     INITIAL_SIZE FINAL_SIZE STARTED               ENDED
------------------------- ------------- ------------ ---------- --------------------- ---------------------
DEFAULT buffer cache      GROW             486539264  536870912 13-jun 08:00:42       13-jun 08:00:42
DEFAULT buffer cache      GROW             536870912  553648128 13-jun 08:05:42       13-jun 08:05:42
DEFAULT buffer cache      SHRINK           553648128  503316480 13-jun 08:06:45       13-jun 08:06:45
DEFAULT buffer cache      GROW             503316480  553648128 13-jun 09:44:45       13-jun 09:44:45
DEFAULT buffer cache      SHRINK           553648128  503316480 13-jun 09:49:46       13-jun 09:49:46