ASMM and poor SQL caching
- From: Susan White <swhite@xxxxxxxxxxxxx>
- To: "'Oracle-L@xxxxxxxxxxxxx'" <Oracle-L@xxxxxxxxxxxxx>
- Date: Fri, 18 Aug 2006 15:53:26 -0500
How does ASMM handle a system with high volumes of non-shareable SQL? When
manually sizing the shared pool, we have always been reminded that a large
shared pool size could lead to serious performance problems strictly because
of the size of the pool. Assuming you have this situation in an ASMM
environment, how does Oracle handle it? Does the shared pool grow so large
that the other auto-sized caches are affected? Do the advisors recommend
increasing the sga_target to accommodate a huge shared pool and if so, what
are the performance ramifications? Are they similar to those encountered
with large shared pools in a manually sized environment?
I realize that one of the answers is to fix the app. However, I'm trying to
understand how ASMM would handle this situation in case it isn't a good
solution for some applications.
Thanks
Susan White
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
Other related posts:
