Table of Contents
Advertisement
Performance Terms
Performance Terms
Following are performance terms used in this book:
concurrency
latency
response time
scalability
service time
think time
throughput
wait time
What is Performance Tuning?
Performance must be built in. You must anticipate performance requirements
during application analysis and design, and balance the costs and benefits of
optimal performance (see
introduces some fundamental concepts:
1-2 Oracle HTTP Server powered by Apache Performance Guide
The ability to handle multiple requests simultaneously.
Threads and processes are examples of concurrency
mechanisms.
The time that one system component spends waiting for
another component in order to complete the entire task.
Latency can be defined as wasted time. In networking
discussions, latency is defined as the travel time of a
packet from source to destination.
The time between the submission of a request and the
completion of the response.
The ability of a system to provide throughput in
proportion to, and limited only by, available hardware
resources.
A scalable system is one that can handle increasing
numbers of requests without adversely affecting response
time and throughput.
The time between the initiation and completion of the
response to a request.
The time the user is not engaged in actual use of the
processor.
The number of requests processed per unit of time.
The time between the submission of the request and
initiation of the response.
Response Time
System Throughput
"Setting Performance Targets"
on page 1-7). This section
Advertisement
Table of Contents
