Performance Interview Questions

How do you decide the load profile for a performance test?

Load, stress, soak and spike testing — what does each answer?

Load: does it meet SLAs at expected traffic. Stress: where does it break and how. Soak: does it degrade over hours (leaks). Spike: does it survive a sudden surge and recover.

Which metrics do you report, and why is average response time misleading?

Report p90/p95/p99 latency, throughput, error rate and concurrency together — averages hide the tail where real users suffer.

How do you build a realistic workload model?

Derive it from production data: transaction mix by volume, think times, session length, peak concurrency and data volumes — then validate the model against a known production hour.

You found a bottleneck. How do you analyse it?

Work from the outside in: confirm it in the client metrics, correlate with server APM traces, then isolate the layer — app CPU, GC, database, cache, external call, or network.

What is load testing, and why does it matter in Performance?

load testing is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply load testing in a production Performance project?

Apply load testing through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is stress testing, and why does it matter in Performance?

stress testing is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply stress testing in a production Performance project?

Apply stress testing through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is spike testing, and why does it matter in Performance?

spike testing is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply spike testing in a production Performance project?

Apply spike testing through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is soak testing, and why does it matter in Performance?

soak testing is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply soak testing in a production Performance project?

Apply soak testing through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is volume testing, and why does it matter in Performance?

volume testing is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply volume testing in a production Performance project?

Apply volume testing through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is baseline tests, and why does it matter in Performance?

baseline tests is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply baseline tests in a production Performance project?

Apply baseline tests through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is workload modeling, and why does it matter in Performance?

workload modeling is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply workload modeling in a production Performance project?

Apply workload modeling through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is concurrency versus throughput, and why does it matter in Performance?

concurrency versus throughput is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply concurrency versus throughput in a production Performance project?

Apply concurrency versus throughput through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is response-time percentiles, and why does it matter in Performance?

response-time percentiles is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply response-time percentiles in a production Performance project?

Apply response-time percentiles through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is error rate, and why does it matter in Performance?

error rate is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply error rate in a production Performance project?

Apply error rate through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is service-level objectives, and why does it matter in Performance?

service-level objectives is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply service-level objectives in a production Performance project?

Apply service-level objectives through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is Little’s Law, and why does it matter in Performance?

Little’s Law is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply Little’s Law in a production Performance project?

Apply Little’s Law through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is bottleneck analysis, and why does it matter in Performance?

bottleneck analysis is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply bottleneck analysis in a production Performance project?

Apply bottleneck analysis through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is CPU saturation, and why does it matter in Performance?

CPU saturation is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply CPU saturation in a production Performance project?

Apply CPU saturation through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is memory pressure, and why does it matter in Performance?

memory pressure is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply memory pressure in a production Performance project?

Apply memory pressure through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is connection pools, and why does it matter in Performance?

connection pools is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply connection pools in a production Performance project?

Apply connection pools through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is database contention, and why does it matter in Performance?

database contention is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply database contention in a production Performance project?

Apply database contention through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is caching effects, and why does it matter in Performance?

caching effects is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply caching effects in a production Performance project?

Apply caching effects through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is warm-up periods, and why does it matter in Performance?

warm-up periods is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply warm-up periods in a production Performance project?

Apply warm-up periods through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is think time, and why does it matter in Performance?

think time is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply think time in a production Performance project?

Apply think time through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is capacity planning, and why does it matter in Performance?

capacity planning is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply capacity planning in a production Performance project?

Apply capacity planning through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is performance budgets, and why does it matter in Performance?

performance budgets is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply performance budgets in a production Performance project?

Apply performance budgets through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.

What is production monitoring, and why does it matter in Performance?

production monitoring is a core Performance concept used to make testing decisions more accurate, repeatable, and aligned with product risk.

How would you apply production monitoring in a production Performance project?

Apply production monitoring through an explicit, repeatable design: define the expected behavior, automate the highest-risk path, capture useful diagnostics, and verify the result against a stable oracle.