When the automatic shared memory management feature is enabled, the internal tuning
algorithm tries to determine an optimal size for
the shared pool based on the workload. It usually converges on this value by
increasing in small increments over time. However, the internal tuning algorithm
typically does not attempt to shrink the shared pool, because the presence of open
cursors, pinned PL/SQL packages, and other SQL execution state in the shared pool
make it impossible to find granules that can be freed. Therefore, the tuning algorithm
only tries to increase the shared pool in conservative increments, starting from a
conservative size and stabilizing the shared pool at a size that produces the optimal
performance benefit.[@more@]
algorithm tries to determine an optimal size for
the shared pool based on the workload. It usually converges on this value by
increasing in small increments over time. However, the internal tuning algorithm
typically does not attempt to shrink the shared pool, because the presence of open
cursors, pinned PL/SQL packages, and other SQL execution state in the shared pool
make it impossible to find granules that can be freed. Therefore, the tuning algorithm
only tries to increase the shared pool in conservative increments, starting from a
conservative size and stabilizing the shared pool at a size that produces the optimal
performance benefit.[@more@]
来自 “ ITPUB博客 ” ，链接：https://blog.itpub.net/10599713/viewspace-996267/ ，如需转载，请注明出处，否则将追究法律责任。
请登录后发表评论
登录
全部评论
-
博文量740
-
访问量2002849
最新文章
- 人力&人手&人才&人物
- oracle树中prior的用法
- Using Supplied Packages to Manage Stored Outlines
- $ORACLE_HOMERDBMSADMIN目录下各SQL的含义
- PRODUCT_USER_PROFILE Table
- Backing Up Server Parameter Files with RMAN
- Backing Up Control Files with RMAN
- Backing Up Individual Tablespaces with RMAN
- Making Whole Database Backups with RMAN
- 目睹奥运火炬传递
