The fundamental measure of performance is response time—the duration that someone spends waiting for an experience to finish. Only by measuring response time can you guarantee that your system is not wasting any of your user’s time.
One of the biggest problems with Oracle Database tuning is that non-technical people (and even a lot of technical ones as well) can’t understand it. Although we invented Method R in an Oracle context, it’s easy to explain our method in everyday terms, because Method R is probably already the method you use to tune everyday things.
Oracle’s and Method R’s performance tools are not mutually exclusive. Just about every Method R customer in the world uses ASH (Active Session History), AWR (Automatic Workload Repository), and OEM (Oracle Enterprise Manager), too.
Toad and the tools offered by Method R are not mutually exclusive. Many Method R customers are also Toad users.
An experience doesn’t have to be broken to be important. Companies that routinely measure the performance of their important user experiences in the Method R way have a much better chance of preventing performance problems so that their users will never even see them.
The diamond in the Method R Corporation logo is the kind of diamond that you see in flowcharts.
Sometimes, people with slow systems say that step 1 of Method R is difficult because every task is important, and every task is slow. Method R was designed in exactly these situations. Even when everything is slow, you see, something is the business’s most important thing to fix first.
Lots of companies, large and small, including companies in the Fortune 100, use Method R software.
The four “magic” questions about performance of course aren’t really magic. They’re actually just four simple questions you naturally ask when something takes too long.
Method R is a commonsense method for optimizing a system. It is the straightforward process of answering the four natural questions about performance: How long? Why? What if? and What else?