Explore >> Select a destination
|
You are here 
|
jonathanlewis.wordpress.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.... | |
| | | | |
tonyhasler.wordpress.com
|
|
| | | | | When a table is accessed by multiple members of a parallel query server set, the execution plan may show the use of block range granules (PX BLOCK ITERATOR) or partition granules (PX PARTITION [RANGE|LIST|HASH] ITERATOR or PX PARTITION [RANGE|LIST|HASH] ALL). The basic ideas surrounding these concepts are discussed in numerous blogs and books, including my... | |
| | | | |
hourim.wordpress.com
|
|
| | | | | The last Jonathan Lewis post on RAC Planswhich finished by the following phrases: "If you're going to hard-code hints into a query then take a look at the outline it generates when it does the right thing, and that will tell you about the 15 or so hints you've missed out. (Better still, consider generating... | |
| | | | |
mauro-pagano.com
|
|
| | | Most of the overall database performance issues (not caused by SQL tuning) are prettycomplex to setup because they require a workload and it takes quite some work to reproduce concurrency in a test environment where at best you got a couple folks testing some new code. Nowadays there are ways to reproduce a realistic workload... | ||
