What is Method R Workbench?
Method R Workbench is a software bundle consisting of the Method R Workbench application, and the Method R Trace extension for Oracle SQL Developer.
The Method R Workbench application is used for processing Oracle Database event 10046 extended SQL trace files. It runs on macOS, Linux, and Microsoft Windows, where it can process trace files generated by an Oracle Database version 11.1 and newer, running on any operating system.
The Method R Workbench target user base is developers, database administrators, decision-makers, and anyone wanting precise measurements of end-user response time experiences with an Oracle-based system.
The main design goals for Method R Workbench are:
- To help you explain exactly why an Oracle-based program consumes the duration that it does.
- To help you predict the precise impact upon such a program duration, expected to result from a proposed change to your system .
- To help you organize and manage all the Oracle trace files you’ll accumulate throughout your application’s life cycle.
Users may access Method R Workbench through a Section 508-compliant (29 U.S.C. 794d) application, or through a scriptable command line API. Users generally transfer trace files from the Oracle Database systems being analyzed to their local machine with the Method R Trace extension for Oracle SQL Developer (included), or with software tools such as FTP or NFS.
The centerpiece of Method R Workbench is a response time profiler called mrprof that creates a richly detailed HTML5 report. The fundamental element that is repeated throughout this report is the profile, which has this basic structure:
|Subroutine||Time (sec)||Call count||Avg. latency|
This format makes simple work of knowing exactly why your application consumes the response time it does. The HTML5 document uses color and structure to guide your analysis. With minimal training, a Method R Workbench user can—in just minutes—identify the root cause of an Oracle-based application performance problem, propose sensible solutions to it, and predict the end-user response time impact of each proposed solution.
In addition to the profiler, Method R Workbench contains a trace file data mining tool called mrskew that helps you answer hundreds of ad hoc performance questions. Among the more than 25 prepackaged mrskew actions are reports like:
- Show the durations experienced by your application users among a directory full of trace files from a connection pool.
- For a loop of SQL executions, show the iteration that takes the most time, along with the input values (“bind variable values”) that drove it.
- Show I/O subsystem latencies grouped by Oracle data file ID.
Method R Workbench also contains other utilities that help with cropping trace files, converting Oracle timestamp data to wall clock times and back, and creating scriptable chains of mrskew reports.
Method R Workbench includes the Method R Trace extension for Oracle SQL Developer. When Method R Trace is enabled, it will create and retrieve an Oracle event 10046 extended SQL trace file that precisely accounts for the execution duration of SQL and PL/SQL within a SQL Developer worksheet. Oracle SQL Developer can be configured to run Method R trace file processors directly from its feature. You can also drag trace files from Oracle SQL Developer and drop them into Method R Workbench.