The Method R Toolbox software package combines the Method R Profiler, our revolutionary response time profiling tool, with Method R Trace, our zero-click performance data collector for Oracle SQL Developer. Method R Trace makes it easy to collect and retrieve perfect Oracle extended SQL trace files. The Profiler gives you the story your trace file has to tell; a complete account of response time for the end-user experience you’ve traced. The Profiler guides you by using structure and color. It’s easy to learn, and it’s easy to run.
Method R makes the best Oracle performance diagnostic tools I have ever used.
Principal Software Engineer with Honors
Performance Problems Can Come from Anywhere
Do you know where software performance problems come from? They can come from anywhere:
- They can come from badly written code, from SQL or PL/SQL or PHP or C# or Ruby;
- They can come from too many index segments, or too few, or a bad decision about your data model or how your schema was implemented;
- They can come from inadequate hardware capacity, or a bad RAID controller, or a mistake in how your SAN caches are configured;
- They can come from a badly set parameter on your OS or database or application server or web server;
- They can come from a user who mentally filters through 10,000 rows of results because she doesn’t know there’s a one-click way to get the one row she really wants;
They can come from anywhere. It’s a big problem.
How Do You Find and Prevent Problems?
There’s a rich Oracle history of trying to find performance problems in perhaps the most inefficient possible way: by looking everywhere they might come from. But because performance problems can come from anywhere, neither you nor your software can possibly monitor and make sense of data coming from everywhere your performance problems might be coming from. You can’t prevent problems this way either: you can’t possibly know everything there is about all the layers in a complex stack of hardware, software, and personnel, before you take an application live. Does an application developer really have to know everything there is to know about Oracle redo and undo and freelists and IOTs before he can write great code that uses an Oracle Database?
There’s a much better way.
I’m a firm believer in the Method R strategy for performance tuning as it has worked well for me countless times over the years.
Sr. Oracle/PeopleSoft DBA
The Way Out: Profiling
A profile is a report of exactly how your system spends your user’s time. It’s how you answer simple-sounding business questions like these:
- That click takes 20 seconds now. It used to take 0.5. Why?
- That report took 2 hours. Could it run in 10 minutes?
As simple as these questions sound, you can’t answer them with the tools you use today. That’s why managing performance is way more difficult for you than it needs to be.
Profiling is what DBAs and sysadmins do in production when a program takes longer than we want, or when we just wonder if it could go faster. Profiling is what developers with good code hygiene do before they hand their code to the next person in the software lifecycle, to make sure their code is as tight and fast as possible—to make sure they didn’t do anything inefficient that might be particularly embarrassing under load.
We’ve always had trace files, but most developers do not know how to read them. The Profiler makes things very easy and gives me the evidence I need to demonstrate the problem is in the code, not the database.
We Get It: Profiling is Hard
Without the right tools, profiling is a nightmare. Profiling with Oracle Enterprise Manager or Oracle’s Active Session History data (if you’re lucky enough to have a license for it) is impossible. The data you need is in your Oracle trace data, but collecting trace data can be difficult. Even if you’ve cracked the collection problems, retrieving trace files can be a pain in the neck, especially for developers and analysts who don’t have login access to the system they’re trying to fix. And making sense of trace files without the right tools can make you go blind. Yet Oracle’s tkprof leaves so much to be desired...
But Profiling is Easy with the Right Tools
The Method R Toolbox pairs of our easiest-to-use trace data collection and retrieval tool and our easiest-to-use profiling tool. The result: you’ll finally find out where all those programs have been hiding your time. You’ll have the tools that many of our customers have used to systematically eliminate waste from their systems, to save enormous heartache and strife. And heat, and electricity, and cash. With our Toolbox, you’ll be able to explain Oracle application response times in a manner that database administrators, developers, users, and managers alike can relate to. Imagine: “Here’s where all of your time has been going...” The Method R Toolbox is performance management software that you need, whether you’re live right now or still building, whether you’re running custom software or software off-the-shelf.
When you combine MR Trace and the Profiler, we’ve been able to turn around fixes with almost no interruptions and have taken warehouse queries that used to never finish down to less than ten minutes.
Orion Data Management
What’s In the Package
Here’s what you get in the Method R Toolbox software package:
- Method R Profiler 1-person license, including maintenance
- Method R Trace 1-person license, including maintenance
Method R Software Information Library
Check out our library for more information about Method R software:
The Fine Print
Here are the definitions of the Method R Software Licensing terms. Don’t hesitate to contact us if you have any questions.
Per-Person License. A Software Per-Person License restricts the number of people who can run the Software. Each Software Per-Person License unit entitles one specific person to run the specified Software on any system, using any login id. A Per-Person license is not transferrable to another person. With a Per-Person license, the distribution contains the licensed software for all the platforms we support.
Per-Instance License. A Software Per-Instance License restricts the number of Oracle Instances with which the Software can run. Each Software Per-Instance License unit entitles any number of users to run the specified Software upon output created by one single Oracle Instance. An Oracle Instance is defined as one set of Oracle background processes/threads and a shared memory area, which is memory that is shared across those processes/threads running on a single computer. For example, a 3-node Oracle Real Applications Cluster (RAC) system, is a 3-Instance system.
Maintenance License. An active Maintenance License entitles a licensee to download and install, at no additional fee, all new versions of the specified Software (for the licensed platforms) that are released within eleven (11) months from the date of purchase. To download and install a version released after this period requires an additional fee.
Oracle is a registered trademark of Oracle Corporation.