本文探讨了在RAC环境中，GC缓冲区繁忙（gc buffer busy）事件与日志文件同步（log file sync）之间的关系。Oracle的ADDM建议，当遇到'log file sync'等待事件导致'gc buffer busy'时，应优先解决日志文件同步问题，因为这可能由硬件因素如存储、板卡或链路造成。GC当前块繁忙等待时间由PIN时间、刷新时间和发送时间组成，其中日志刷新时间对整体服务时间影响显著。同时，'gc buffer busy acquire/release'是并发访问同一数据块时产生的衍生等待。优化日志IO性能对于RAC系统的整体性能至关重要。
这篇博文整理自我的帖子： RAC中的gc current block busy与redo log flush
对于log file sync(本质上是 write redolog慢)引发gc buffer busy acquire /release 集群等待事件的这个命题的真伪，其实Oracle在开发性能调优组件ADDM时一早给了我们答案：
RECOMMENDATION 2: Host Configuration, 12% benefit (507182 seconds)
ACTION: Investigate the possibility of improving the performance of I/O
to the online redo log files.
RATIONALE: The average size of writes to the online redo log files was
40 K and the average time per write was 10 milliseconds.
ADDITIONAL INFORMATION:
Waits on event “log file sync” were the cause of significant database
wait on “gc buffer busy” when releasing a data block. Waits on event
“log file sync” in this instance can cause global cache contention on
remote instances.
如果你在ADDM(?/rdbms/admin/addmrpt)中找到上述文字，那么基本可以确认gc buffer busy的源头是log file sync(虽然本质上不是)，那么优先解决
最低0.47元/天 解锁文章
1306
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
