Performance

Management
1

Performance Management
Performance Management

When dealing with performance management,

we're talking about the continuous process of
evaluating a server to determine whether or not
it can deliver the level of performance that's
required.
Example: the server's ability to handle a certain
load of concurrent users. Performance
management is closed linked to capacity
planning; the difference is that performance
management involves tuning the current
system so that it can perform better, thereby
enabling it to support more users. Capacity
planning, on the other hand, focuses on how
many users a site can support and how to scale
the site so it can support more users.

Performance Management
The goal of performance
management is to make the best
use of your current resources, to
meet your current objectives
without excessive tuning effort.

Performance Management
Service level agreement (SLA)
The concept of SLA was introduced in order to
match business needs specified with
subjective perceptions. The SLA is a contract
that objectively describes and enforces such
measurements as:
_ Average transaction response time for
network, I/O, CPU, or total
_ The distribution of these response times (for
example, 90% TSO trivial transactions at less
than 200 millisecods )
_ System availability metrics

Performance Management Flow Chart

General performance management metrics

In performance management there are some
metrics in order to verify the system behavior
towards SLA and performance in general.

Average transaction Response Time (Tr)

External Throughput Rate (ETR)
Resource Utilization (U)
Saturation Design Point (SDP)

General performance management metrics

Average Transaction Response

Time (Tr)
Transaction : Work produces by the interaction
of user and system.
Transaction time : Response time + User think
time
Response time : (Online ) user hits the enter
key and a screen with the required full data is
presented at the screen.
Response time : service time (the time actual
work is done) + waiting time (the time
waiting for resource).

General performance management metrics

External Throughput Rate

(ETR)
It is the measurement of the number of ended
transactions per elapsed time.
Also known as transaction rate.
ETR = N / (Tt + Tr)
N Is the average number of users sending
transactions (logged on)
Tt Is the average thinking time of these users
Tr Is the average response time

General performance management metrics

Resource Utilization (U)

Resource utilization measures how much a
resource delivers service in a timely basis.
U% = Ts ETR 100
If in a bank branch office with only one teller
there ia an average arrival rate of 2
clients/minute with a service time (Ts) of 0.25
minute, we can say that the teller average
utilization is U% = 0.25 * 2 * 100 = 50%
9

General performance management metrics

Saturation design point

(SDP)
A CPU is either in busy state or in wait state.
In other words, either it is instantaneously
100% busy or 0% busy
"If my hourly utilization is 75%, how often did I
reach 100% in the per minute average within
this hour?
Ans: the concept of Saturation Design Point
(SDP), the maximum average utilization in a
larger interval, , where the installation is sure
that in the smaller interval the average

10

Processor performance metrics

CPU Time
Cycle Time
Cycles per Average Instruction
Path length
Internal Throughput Rate (ITR)

11

Processor performance metrics

CPU time
CPU time of a transaction is the processing
time consumed to execute the program logic
of the transaction.
In performance management, the target is to
reduce such amount.
CPU time = Cycle_Time * CPAI *
Path_Length
12

Processor performance metrics

Cycle time
Cycle time depends on the time to transport
the pulse across the circuitry and the switch
time, that is the time to invert the 0s to 1s
and vice-versa within the boolean circuits.
Smaller the cycle time faster the processor
and less CPU time consumed.
.

13

Processor performance metrics

CPAI - Cycle per average
instruction
The number of cycles, in average, needed to
execute one instruction.
Depends very much on the set of executed
instructions. There are instructions executed
in just one cycle.
On the other hand, there are complex
instructions that need many cycles in order to
execute, biasing consequently the CPAI to a
higher value.
14

Smaller the CPAI, the better. In one machine

the CPAI depends on the design. Better the

Processor performance metrics

Path length
Path length is the number of instructions
needed to execute the transaction program
that consumed the CPU time.
If you have less path length, this produces a
less CPU time.
Path length depends on:
Processor architecture, which defines the set
of instructions and
Quality of the compiler that generates the
object code.

15

Processor performance metrics

Internal throughput rate (ITR)

ITR determines the capacity of a processor in

terms of the number of transactions per CPU
second.
ITR is a function of:
CP speed. Faster the CP, higher the ITR.
Operating system. Better the operating
system, higher the ITR.
Transaction workload characteristics. Short
trivial transactions produce a higher ITR.
16

Performance Management
I/O performance and metrics
As CPU speed increases, the I/O response
time (I/O Tr) become the determinant factor in
the average transaction response time.
We can get excellent transaction response
time gains by reducing I/O wait time (Tw) and
I/O service time (Ts).

17

Performance Management
Network Performance
Management
It consists of measuring, modeling, planning,
and optimizing networks to ensure that they
carry traffic with the speed, reliability, and
capacity that is appropriate for the nature of
the application and the cost constraints of the
organization.
Not all networks are the same. As data is broken
into component parts (often known frames,
packets, or segments) for transmission,
several factors can affect their delivery.

18

Performance Management
Factors affecting network
performance

Bandwidth : maximum rate that information

can be transferred. (bits/second)
Throughput: actual rate that information is
transferred.
Latency: delay between the sender and the
receiver decoding it, this is mainly a function
of the signals travel time, and processing
time at any nodes the information traverses.
(speed limit.)
Jitter: variation in the time of arrival at the
receiver of the information.

19