|
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
|
|
| | | | | 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. | |
| | | | |
tanelpoder.com
|
|
| | | | | Jonathan Lewis has already written about this behavior from the angle of PARALLEL hints. I'm writing a similar article just because the word FORCE in the ALTER SESSION FORCE PARALLEL QUERY syntax. Force should mean that some behavior would always happen (when possible), right? Let's test: SQL> CREATE TABLE t AS SELECT * FROM dba_objects; Table created. SQL> CREATE INDEX i ON t(owner); Index created. SQL> @gts t Gather Table Statistics for table t... PL/SQL procedure successfully completed. Now let's "force" the parallel query in my session, run the query and check the execution plan: - Linux, Oracle, SQL performance tuning and troubleshooting training & writing. | |
| | | | |
rwijk.blogspot.com
|
|
| | | |||