Performance Test Result Analysis – Intermediate
As you go to the following level, known as the Intermediate level of performance test result analysis, you will gain knowledge on how to read various graph kinds. You gained a thorough understanding of the fundamental graphs used in Performance Testing in the previous post, which could be used to provide a solid foundation for the analysis of the results. You will now have a thorough comprehension of all those graphs as we move forward. The analysis of client-side, server-side, and network monitoring graphs is included in this post. You’ll learn how to combine the various graphs to spot the bottlenecks. This level is broken down into three sections to facilitate understanding:
1. Client-side result analysis:
The study of client-side graphs and metrics is covered in this section. All of the client-side data are gathered by a performance testing tool, which then shows them either in real-time or at the conclusion of the test. The basic starting point for the examination of the bottlenecks is client-side metrics. They provide you with a hint and suggest what you should look into. As an illustration, if out of 10 transactions, two violated the response time NFR, you should begin looking into the underlying cause that affected those two transactions.
The User graph, Response Time graph, Throughput graph, and others are examples of client-side graphs.
2. Server-side result analysis
The examination of server-side metrics is covered in this section. The server-side statistics need to be gathered using a monitoring tool for applications. The precise location of the hidden bottleneck will be revealed by following the hint provided by the client-side graph and connecting it with the server-side metrics.
Server-side statistics include graphs of the fundamental CPU and Memory utilization, as well as GC analysis and heap dump analysis.
3. Network-side result analysis:
The network’s performance metrics are covered in this section. These measurements assist in identifying network bottlenecks that increase latency. Low bandwidth is one of them that happens frequently.
Let’s begin by analyzing the results of the client-side performance test.
