The correct identification of code hot spots areas is our way of fixing them. We explored different behavior for application bottlenecks or hot spots and grouped them into different root causes. Then, according to the root causes, we can propose our fix.
In the subsequent chapters, we will modify this strategy a little, but for now, because we have learned different CPU time profiling readings, let's draft our fixing strategy.
In the following diagram, we have to answer the first question, which determines our strategy flow: Is the method performance bad? or is it the method invocation count?: