|
|
inside Spotlight on Oracle
| |
All of the following articles on Spotlight on Oracle may be viewed free of charge. You have permission to distribute these materials within your company; but you may not, however, re-publish any articles without first asking for permission.
Thanks, Guy.
 Diagnosing and Solving Oracle Parsing Issues
Minimizing parsing is critically important both to reduce the CPU overhead of parsing, and to reduce the latch/mutex contention that usually accompanies excessive hard parse rates. Using bind variables in application code is the best way to achieve this, though the CURSOR_SHARING parameter can also be very effective. Spotlight 6.1 has new diagnostics to help you identify and correct bottlenecks caused by excessive parse rates.
|
Optimizing the Oracle 11g Result Cache
The Oracle 11g Result Set Cache stores entire result sets in shared memory . If a SQL query is executed and it’s result set is in the cache then almost the entire overhead of the SQL execution is avoided: this includes parse time, logical reads, physical reads and any cache contention overhead (latches for instance) that might normally be incurred.
In this article Guy shows how applying the result set cache to all SQLs is unlikely to be effective and can lead to significant latch contention.
| |
|
|