本文讨论了Exadata中Cell Single Block Physical Read事件的原因及其优化策略。该事件通常发生在索引查找过程中，当所需块不在内存中而必须从Exadata存储单元磁盘读取时。文章提供了几种解决方案，包括审查CellSingleBlockPhysicalReadLatency指标、调整SQL语句减少读取的块数及改进索引使用等。
This is an Exadata wait event similar to db file sequential read and normally occurs during index lookups when the block is not in memory and must be read from the Exadata storage cell disks. These are generally considered a ‘good’ read unless the index being used is not very efficient. In this case the query will read more blocks than necessary and possibly age out other good blocks from the Exadata smart cache.
Solutions
Review the ‘Cell Single Block Physical Read Latency’ metric (in Ignite Resources view on the Exadata tab) to determine latencies. If the time to read data is above 2ms, that could indicate configuration issues with the Exadata storage cell.
If there are excessive waits on this event for a specific SQL statement, tune the statement so that it reads fewer blocks. If the top objects listed in the Ignite Object tab are indexes, determine if there is a more efficient index that could be used. If the top objects are tables, Oracle is going back to the table to get more data after the index lookup completes. That may indicate criteria in the WHERE clause that is not using a column in this index. Adding that column to the index could help performance.
DML statements like INSERT, UPDATE, DELETE, etc can also wait on this event because they are being forced to update inefficient indexes. Review the Ignite Object tab to determine which indexes are being waited for. If they are inefficient, Oracle is most likely not utilizing them in other SQL statements, so consider dropping them
扫一扫
1万+
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
