Bottleneck A bottleneck is a point in an application where congestion and delay occur, slow ing down the processing of requests

and causing users to experience unacceptable service delays. Capacity The capacity of a system is the total workload it can handle without violating p redetermined key performance acceptance criteria. Capacity test A capacity test complements load testing by determining your server s ultimate fai lure point, whereas load testing monitors results at various levels of load and traffic patterns. You perform capacity testing in conjunction with capacity plan ning, which you use to plan for future growth, such as an increased user base or increased volume of data. For example, to accommodate future loads, you need to know how many additional resources (such as processor capacity, memory usage, d isk capacity, or network bandwidth) are necessary to support future usage levels . Capacity testing helps you to identify a scaling strategy in order to determin e whether you should scale up or scale out. Endurance test An endurance test is a type of performance test focused on determining or valida ting performance characteristics of the product under test when subjected to wor kload models and load volumes anticipated during production operations over an e xtended period of time. Endurance testing is a subset of load testing. Horizontal scaling Adding more computer systems (servers) to the environment. See also: Vertical sc aling Instrumentation Inserting (either statically or dynamically) code around program events in order to capture performance data. See also: Profiling Latency In general terms, a time delay between the moment something is initiated, and th e moment one of its effects begins. In the realm of software performance, latenc y is often referred to in the contexts of server latency, network latency and di sk latency. Load Test A performance test focused on determining or validating performance characterist ics of the product under test when subjected to workload models and load volumes anticipated during production operations Performance Performance refers to information regarding your application s response times, thr oughput, and resource utilization levels. Performance test A performance test is a technical investigation done to determine or validate th e speed, scalability, and/or stability characteristics of the product under test . Performance testing is the superset containing all other subcategories of perf ormance testing. Profiling The insertion of tools into program code that traces events captures metrics as the program is running. Examples of java profiling tools are JProbe, JXInsight a nd dynaTrace. Also see: Instrumentation

Response time Response time is the amount of time that it takes for a server to respond to a r equest. Saturation Saturation refers to the point at which a resource has reached full utilization Scalability Scalability refers to the ability to handle additional workload, without adverse ly affecting performance, by adding resources such as CPU, memory, and storage c apacity. SLA Service Level Agreement. In the context of performance testing, it is often the required level of performance (response time), availability (up time) or both. Spike test A spike test is a type of performance test focused on determining or validating performance characteristics of the product under test when subjected to workload models and load volumes that repeatedly increase beyond anticipated production operations for short periods of time. Spike testing is a subset of stress testin g. Stress test A stress test is a type of performance test designed to evaluate an application s behavior when it is pushed beyond normal or peak load conditions. The goal of st ress testing is to reveal application bugs that surface only under high load con ditions. These bugs can include such things as synchronization issues, race cond itions, and memory leaks. Stress testing enables you to identify your applicatio n s weak points, and shows how the application behaves under extreme load conditio ns. Throughput Throughput is the number of units of work that can be handled per unit of time; for instance, requests per second, calls per day, hits per second, reports per y ear, etc. Utilization In the context of performance testing, utilization is the percentage of time tha t a resource is busy servicing user requests. The remaining percentage of time i s considered idle time. Vertical scaling Adding more (or faster) CPUs within the same computer system. See also: Horizont al scaling