/explore
|
You are here 
|
blog.tanelpoder.com | ||
| | | | |
dincosman.com
The performance issue with an SQL query was resolved by using the /*+ PARALLEL(2) */ hint, reducing execution time from 180-200 seconds to milliseconds. The decision to perform a direct read from disk to memory instead of reading blocks from disk was made by the database engine and is controlled by the hidden "_serial_direct_read" parameter.... |
|
| | | | | ||
| | | | |
tanelpoder.com
Training overview This training session is entirely about making Oracle SQL execution run faster and more efficiently, understanding the root causes of SQL performance problems and Cost Based Optimizer misbehavior. Instead of looking into increasing system utilization (by using more buffer cache or more parallelism) as a first "tuning" choice, this class is mostly about decreasing resource usage of SQL execution plans by improving their shape and available access paths. - Linux, Oracle, SQL performance tuning and troubleshooting training & writing. |
|
| | | | | ||
| | | | |
tanelpoder.com
Snapper used to require access to DBMS_LOCK, so it could sleep for X seconds between the "before" and "after" performance data snapshots. Now it is possible to get away without using DBMS_LOCK. Instead you will run Snapper twice, once for taking the "before" snapshot, then run your workload and then run Snapper again for taking the "after" snapshot and print the output. So, the usual way of running snapper is this: - Linux, Oracle, SQL performance tuning and troubleshooting training & writing. |
|
| | | | | ||
| | | | |
blog.toadworld.com
Why my execution plan has not been shared - Part I |
|
| | | |||
