Database Reference
In-Depth Information
Part IV
Optimization
Engineering isn't about perfect solutions; it's about doing the best you can with limited
resources.
— Randy Pausch, The Last Lecture . 2008.
Only once you have identified the root cause of a performance problem should you try to solve it. Regardless
of the problem you are facing, the essential goal to achieve is reducing—or, even better, eliminating—the time
spent by the most time-consuming operation. Note that a single operation may be composed of many actions
that are executed one by one. For example, many fetches are necessary in order to fully process a query
returning many rows.
Chapter 11 describes the available SQL optimization techniques, and goes on to explain how to choose
between them. Chapter 12 describes how parsing works, how to identify parsing problems, and how to
minimize parsing's impact without jeopardizing performance. Chapter 13 describes how to take advantage
of available access structures in order to efficiently access data stored in a single table. Chapter 14 goes
beyond accessing a single table by describing how to join data from several tables together. Chapter 15 deals
with parallel processing and the techniques used for speeding up stream inserts, and for minimizing the
interactions between components. Finally, Chapter 16 describes how physical storage parameters have an
observable impact on performance. Simply put, the aim of the chapters in this part is to show how to improve
the response time of operations interacting with the SQL engine by taking advantage of the many features
provided by Oracle Database for that purpose.
 
Search WWH ::




Custom Search