On January 27, my dear friend Mogens Nørgaard hosted me for a 1:39:13 chat, which he flatteringly called “Cary Millsap – the master thinker of application performance and more.” It’s a long, wandering conversation that I really enjoyed. Here’s how my friend Mogens describes it:
From Oracle Database 12.1 onward, the JDBC driver provides a convenient method called setClientInfo to set user session handle attributes in the database. There are three user session handle attributes that are useful when instrumenting your application so that it identifies itself and exposes its actions in Oracle Database (such as in the V$SESSION view): […]
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.
Two or three times in the past twenty years, we’ve created Forum pages where people can ask their Method R support questions, and then people can both see other people’s answers and contribute their own. It has gone kind of like this: Me: I’m going to create a new Method R forum. It will become a vibrant […]
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.