How to analyze the data
Following the Optimization Cycle, we must analyze the measurement result to understand the following:
- Can the application performance be improved?
- Where should we focus first?
- How can we improve it?
- Where is the bottleneck?
For example, if we analyze Figure 13.3, the handler spends most of its time on the MongoDB find operation. This means that we should focus on that part, trying to check whether the following applies:
- We have set the connection pool correctly
- We have created a dedicated index
Based on whether this is the case or not, you can define some boundaries that can be further optimized in the next Optimization Cycle step.
Of course, when monitoring all the application’s routes, we will need many filters to select all the routes that require our attention, such as slow endpoints or APIs with a high error rate.
Note that, at times, the data cannot be as detailed as in this example. Let’...
