Performance metrics (response time, throughput) in Testing Fundamentals - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is response time in performance testing?

Response time is the total time taken from sending a request to receiving the complete response. It measures how fast a system reacts to a user action.

beginner

Define throughput in the context of software performance.

Throughput is the number of transactions or requests a system can handle in a given time, usually measured as requests per second or transactions per minute.

intermediate

Why is measuring response time important for user experience?

Because users expect quick feedback, slow response times can frustrate users and cause them to leave. Measuring response time helps ensure the system feels fast and responsive.

intermediate

How does throughput differ from response time?

Response time measures how fast one request is handled, while throughput measures how many requests the system can handle over time. They show different aspects of performance.

beginner

Give a real-life example to explain throughput.

Imagine a cashier at a store: throughput is like how many customers the cashier can serve in an hour. The faster they serve, the higher the throughput.

What does response time measure?

A Time taken to complete one request

B Number of requests per second

C Total users on the system

D Amount of data transferred

Response time measures how long it takes to complete a single request from start to finish.

Throughput is best described as:

A Speed of a single request

B Number of errors in requests

C Number of requests handled in a time period

D Memory used by the system

Throughput counts how many requests or transactions the system processes in a given time.

If a system has low response time but low throughput, what does it mean?

A It handles many requests slowly

B It handles few requests slowly

C It handles many requests quickly

D It handles few requests quickly

Low response time means fast handling per request, but low throughput means few requests handled overall.

Which metric would you check to know how many users can be served simultaneously?

A Throughput

B Response time

C CPU usage

D Disk space

Throughput indicates how many requests or users the system can handle at once or over time.

Why is it important to monitor both response time and throughput?

A They measure the same thing

B To understand speed and capacity of the system

C Only response time matters

D Only throughput matters

Response time shows speed per request; throughput shows how many requests the system can handle. Both are needed for full performance insight.

Explain the difference between response time and throughput using a simple example.

Think about how fast one task is done versus how many tasks are done in total.

Why should testers measure both response time and throughput during performance testing?

Consider what each metric tells about the system.