Summary

We began this chapter by understanding the mindset we should have when profiling performance in our applications to make decisions—that of measure twice, cut once—to ensure that we had sufficient data before we acted. From this, we looked into a structured methodology, OODA, to help us make informed decisions in profiling and understanding the performance of our Apex code.

We looked at the four steps of OODA individually and how they fit into a broader whole to help us profile, analyze, decide, and act on our code as part of a performance analysis system. From this, we looked into more details of how we perform the analysis required in the Orient phase using big O notation and magnitude analysis. Although this involved some basic algebra and mathematics, it provided us with a simple way of reviewing and understanding how to quantify and communicate the impact of the specific processes we had implemented.

With this tool available to us, we saw specifically...