Creating “high performance” as an attribute of complex software is extremely difficult business for developers, technology administrators, architects, system analysts, and project managers. However, by understanding some fundamental principles, performance problem solving and prevention can be made far simpler and more reliable.
One of the more challenging types of performance problem is the dreaded scenario in which the problem occurs only intermittently and is difficult to trap with your performance measurement tools. In such a situation, trace data can be an irreplaceable ally, allowing you to understand even phenomena that you’ve not yet actually measured.
Cary Millsap’s The Method R Guide to Mastering Oracle Trace Data, 2nd edition contains everything you need to know about Oracle trace data—how to collect it and what to do with it once you have retrieved it, using the Method R Workbench software suite. The book creates a scientific basis for understanding why computing systems perform the way they do. It provides comprehensive detail about controlling, […]
Do you have SQL in your system that doesn’t use placeholders, like this? [3r3dhkb0z824v] select stuff from t where id=18432... [5wamvs45j6nh4] select stuff from t where id=4286... [ih5x9lgg492nk] select stuff from t where id=329971... Statements like these are generated dynamically by procedural programs written in Java, PHP, C#, etc. (or even PL/SQL if you work really […]
Connection pools help solve a big performance problem, but they also make using trace data more difficult. Method R Tools, part of the Method R Workbench software package, makes it easier to measure individual user response time experiences on connection pooling systems. Now you can look at performance problems the way you’ve always wanted to see them.