Performance Testing Fundamentals

To answer this question, the user needs to have knowledge about the different options available in the Analysis tool of load testing software.

Option A: Drill Down is a feature that allows the user to view more detailed information about a specific data point in a graph. It does not provide an option to see the results of two graphs from the same load test scenario in a single graph.

Option B: Apply Filter allows the user to filter the graph data, for example, by selecting a specific time range, HTTP response code, or transaction name. It does not provide an option to see the results of two graphs from the same load test scenario in a single graph.

Option C: Merge Graphs is the correct answer. This option allows the user to combine two or more graphs from the same load test scenario into a single graph. This is useful when you need to compare the results of different load tests or different types of data.

Option D: Auto Correlate is a feature that automatically detects and correlates dynamic values in a load test script. It does not provide an option to see the results of two graphs from the same load test scenario in a single graph.

Therefore, the answer is:

The Answer is: C. Merge Graphs

LoadRunner analysis graphs include 'Network Delay Time' which shows the complete round-trip delay between source and destination machines. 'Time to First Buffer' measures server response time, not network path delay. MS IIS and Windows Resource are server metrics, not network path analysis.

When throughput plateaus (becomes flat) despite increasing virtual users, the most common cause is bandwidth saturation - the network pipe is maxed out. Database, web server, or application server connection issues typically cause errors or degraded response times rather than flat throughput. Bandwidth constraints create a hard ceiling on throughput.

The 'Transaction Response Time (distribution)' graph plots transaction response times on the X-axis against the number of transactions (count/frequency) on the Y-axis, showing the distribution pattern. 'Transactions per Second' shows transaction rate over time. 'Average Transaction Response Time' shows the mean response time trend. 'Transaction Response Time Under Load' correlates response time with load levels.

HTTP status code 500 (Internal Server Error) indicates a generic server-side error, representing application crashes or failures under load. Codes 400 (Bad Request), 401 (Unauthorized), and 403 (Forbidden) indicate client-side errors rather than server failures.

Poor database design, inefficient session/state management, and high queue length on the server directly degrade response times. High CPU usage is typically a symptom or cause of resource saturation rather than a direct software/architecture-based bottleneck.

The question asks which counter is NOT a memory-related performance counter. % User Time is a CPU performance counter that measures the percentage of time the processor spends in user mode, not memory utilization. Available Memory Bytes, Committed Memory Bytes, and Memory Pages/second are all genuine memory-related counters that track memory availability, allocation, and paging activity.