Three ways to describe Oracle optimization R (method R)

R represents response time (response times). The specific definition is as follows:

1. Target the tasks this are critical to the business.

2. Collect properly scoped, un-aggregated profile data for each task while the task are exhibiting the behavior you want to Record

3. React with the candidate repair that would have the greatest net payoff to the business.

A. Stop if the cost of the repair exceeds the cost of the problem.

4. Go to step 1.

The core element of this is profile. Profile to provide a detailed description of the application's response time to the end user. This layer of Oracle database is the SQL Trace data to be extended.

There is some similarity between the R method and some of our known database optimization methods, but Cary Millsap claims that the R method is the best and most comprehensive of the Oracle optimization methods currently known. Let's take a look at some simple comparisons:

R Method vs oWI method

OWI (Oracle wait interface) is just a basic element in the R method. The R method is applicable to a broader diagnostic guidance strategy (for example, the application layer) (see also: How to "an" application easy to diagnose);

R Method vs YAPP

Interestingly, the process of YAPP (yet Another performance Profiling method) is as follows:

1, get the service time and wait time and its components

2. Sort all the components

3. Optimize each part sequentially

4, to each item in the table, reduce the cost of each execution or the number of executions

Let's look at Descartes ' methodology:

Never accept any truth which is not clear to me, that is, to avoid recklessness and prejudice as far as possible, only to be very clear and determined according to one's own judgment, without any doubt of the truth of the place.

The complex problem that can be studied, as far as possible to decompose into a number of relatively simple small problems, one by one to solve separately.

Move these small problems from simple to complex, starting with easy to solve problems.

After all the problems have been solved, and then combined to test, see whether complete, whether the problem is completely solved.

YAPP is but a form of Descartes ' methodology.

YAPP is only applicable to Oracle layer, and can not be used for WEB application layer; The R method is more widely applicable (in fact, the evolutionary version of YAPP); YAPP is also uncertain about Oracle's idle events.

R Method vs Bottleneck analysis (bottleneck)

Bottleneck analysis is the first to find bottlenecks, R method is targeted task-oriented, focusing on the business. Directly grasp the most concerned angle.

Although the application is not wide enough now, the R method is a theoretically perfect method. The idea of production is worthy of our deep thinking.