Moving to the next level named as Intermediate level of performance test result analysis; you will learn how to read the different types of graphs. In the previous post, you got a high-level knowledge of Performance Testing basic graphs which might help to build a strong platform of the result analysis. So, moving ahead, you will get an in-depth understanding of all those graphs now. This post includes the analysis of client-side, server-side and network monitoring graphs. You will see how to merge the different graphs to identify the bottlenecks. To get a better understanding, this level is divided into 3 parts:
1. Client-side result analysis:
This part covers the analysis of client-side graphs and metrics. A performance testing tool gathers all the client-side metrics and displays them either during the test or at the end of the test. Client-side metrics are the initial points to start the investigation of the bottlenecks. They provide a clue and guide you on what to investigate? For Example: Out of 10 transactions, if 2 transactions breached the response time NFR then you start the investigating the root cause which impacted those 2 transactions.
Some of the client-side graphs are User graph, Response Time graph, Throughput graph etc.
2. Server-side result analysis
This part covers the analysis of server-side stats. An application monitoring tool needs to be set-up to collect the server-side stats. Following the clue getting from the client-side graph and correlating with the server-side metrics will provide the exact address of hidden bottleneck.
Server-side stats include GC analysis, Heap dump analysis along with basic CPU and Memory usage graph.
3. Network-side result analysis:
This part covers the performance metrics of the network. Such metrics help to find out the obstacles of the network which increase the network latency. Low bandwidth is one of them which occurs so often.
So, let’s start with Client-Side Performance Test Result Analysis.
You may be interested: