- 最后登录
- 2023-8-16
- 在线时间
- 1686 小时
- 威望
- 2135
- 金钱
- 50532
- 注册时间
- 2011-10-12
- 阅读权限
- 200
- 帖子
- 5207
- 精华
- 39
- 积分
- 2135
- UID
- 2
|
2#
发表于 2012-4-27 22:58:47
Performance tips:
1. Streams pool sizing
In Oracle 9i, Streams stored its events in the shared pool of the SGA. With Oracle database 10g, a separate pool was introduced into the SGA for Streams.
---- 9i----
Each capture process requires 10Mb of shared pool. In addition to the memory required for the capture process, there is an in-memory buffer queue which holds all of the logical change records (LCRs) for streams requires memory from the shared pool. The buffer queue memory requirement is limited to 10% of the memory allocated with the shared_pool_size parameter.
When the buffer queue memory threshold is exceeded, LCRs will spill-over to disk and continue to spill to disk until all transactions have been consumed by all down-streams sites. When this spill-over occurs, streams performance is impacted.
As of 9.2.0.5, the percentage of shared_pool_size can be modified with the hidden parameter _first_spare_parameter.
---- 10g ----
The Streams memory can be explicitly specified with the streams_pool_size initialization parameter. Streams pool can be autotune when using 10gR2. Prior to this release, the streams pool sizing was managed statically.
Size the streams pool appropriately for the anticipated workload. Use the V$BUFFERED_QUEUES view to identify the total number of messages in the queue and the number of messages spilled to disk while Streams is running. This view also includes statistics on the cumulative number of messages and spilled messages so the streams pool size can be tuned.
9i 中 streams 的相关数据 缓存在 shared pool 中 , Streams Pool流池是 10g引入的新特性 ,streams_pool_size 也是10g新特性 |
|