During design discussions the performance test team observed that database stored procedures for several popular use cases may be badly coded. Which of the following common performance failures would best confirm the team's confirm was justified?

Inefficiently coded database stored procedures often create performance bottlenecks that are not apparent at low load levels. Such code may consume excessive resources (e.g., CPU, I/O) or cause resource contention (e.g., table or row locks). With a single user, the impact might be negligible. However, as concurrent user load increases to moderate or heavy levels, the competition for these shared database resources intensifies. This leads to queuing, increased wait times, and a non-linear degradation in response time. Observing this specific pattern—slow response that manifests and worsens under increasing load—is the strongest confirmation that the underlying code does not scale efficiently.

A. Slow response under all load levels suggests a fundamental, constant inefficiency, but it fails to capture the critical aspect of scalability, which is the primary concern in performance testing.
C. Degraded response over time is a classic symptom of resource leaks (e.g., memory leaks, unclosed database connections), not necessarily inefficient query logic which is typically exposed by load.
D. This describes a failure in reliability or robustness (how the system handles overload), not a direct performance failure related to response time under expected heavy load. ---

1. ISTQB® Certified Tester Foundation Level Performance Testing Syllabus Version 1.0 (2018). Section 3.3.1, "Performance Bottlenecks," states: "A bottleneck is a component of a system that restricts the throughput... Bottlenecks are typically found when the system is operating under heavy load." This supports the principle that performance issues like those from bad code are confirmed under significant load.

2. Jain, R. (1991). The Art of Computer Systems Performance Analysis. Wiley. In Chapter 34, "An Example of a Client/Server System Analysis," the text illustrates how increased user load leads to contention for server resources (CPU, disk), causing response times to increase sharply. This demonstrates that performance limitations are exposed by moderate-to-heavy load. (See Section 34.3, p. 601).

3. Hellerstein, J. M., Stonebraker, M., & Hamilton, J. (2007). Architecture of a Database System. Foundations and Trends® in Databases, 1(2), 141–259. In Section 4.3, "Concurrency Control and Recovery," the authors discuss how locking mechanisms, essential for correctness, can become a major performance bottleneck under concurrent workloads, leading to degraded transaction throughput and increased latency. This directly links concurrent load to performance degradation caused by how database operations are managed. (DOI: https://doi.org/10.1561/1900000002).