You were brought to this page based on an internet search
and as a free service to Oracle DBAs.
The text below is an except from the book,
Oracle Performance Firefighting, written by
Craig Shallahamer of
OraPub, Inc.
Figures and tables are not included on this page, only their reference.
To order the book in either print or PDF form, click
here.
©2009, 2010 by Craig Shallahamer. This is copyrighted material.
PleaseOut of respect for those involved in the creation of the book and also for
their familes, we ask you to respect the copyright both in intent and deed. Thank you.
-------------------------------
Even wait-event analysis falls short compared to ORTA, because ORTA encapsulates wait-event analysis and takes it further. Shunning the advantages of ORTA and relying solely on a wait-event analysis will limit performance analysis in depth and scope, and opens up the possibility of a misdiagnosis. Those are condemning statements, but as you read this book, you will discover that they are true. Here, I will introduce the background and concepts of ORTA. In Chapters 5 and 9, I will detail how to perform the analysis, where to gather the necessary data, and other interesting details.
Response-time analysis did not originate from the firefighting world. It is from the infrastructure planning world of IT. The infrastructure community looks at IT as a network of services and conduits to those services. Translating this to DBA-speak, that would be a bunch of servers networked together. When a user makes a request, it is routed into the mystical IT cloud, where the request waits to be serviced and receives service from a potentially large number of service providers. One way to categorize this time is to place it into two buckets: time being serviced and time waiting to be serviced, or more simply, service time and queue time. Adding the two results gives you the response time. In the course of my Oracle forecasting and predictive analysis work, I noticed that response-time analysis could be applied to firefighting.
As I noted, this type of analysis deals with two high-level time categories: service time and queue time. From an abstracted performance analyst perspective, queue time contains all the time an Oracle process is waiting to be serviced. Service time is all the time the transaction is being serviced. Add all that time together, and you have how long it took for the database transaction to complete; that is, its response time. But it gets better! Since ORTA is used both when firefighting and forecasting, it can serve as a bridge between the two, allowing you to predict the effects of the solution. (Although this book does not focus on the predictive aspect of performance analysis, I will introduce the subject in Chapter 9.)
©2009, 2010 by Craig Shallahamer. This is copyrighted material.
PleaseOut of respect for those involved in the creation of the book and also for
their familes, we ask you to respect the copyright both in intent and deed. Thank you.
|