Any Performance Management or Capacity Planning Project
As an independant consultant since 1988 many projects on
many topics have been worked on. All areas of z/OS tuning,
WLM, PR/SM, hardware selection, hardware differentiation,
DASD and I/O. My extensive background in Capacity Planning provided an excellent background to become an expert is IBM's z/OS Software Pricing. Those projects are described here.
Free initial telephone
consultation so call or write with your project idea and we
can talk about how Al can help!
Capacity Planning's primary role is to forecast workload demand
over some future timeframe and the corresponding service levels
that will be provided at the maximum forecast workload level. If
the projected service level is insufficient to meet the applicable
service-level requirements, Capacity Planning is charged with recommending
configuration changes that will provide adequate performance at
the demanded throughput level.
Similar to performance management your service level requirements
and objectives are important to capacity planning. Utilization is
typically the first measurement discussed with capacity planning,
but many other metrics are also required to monitor and manage the
system's capacity. These include:
- Measures of occupancy of tangible resources, such as control
units, devices, memory, CPU; by workloads.
- Measures of the utilization of resources or services such as
jobs, transactions, CPU hours, I/Os, etc.
- Response time, throughput, service time, percents within targets,
- System Behavior
- Measures of internal logical behavior such as queues lengths,
- Latent Demand
- As any system approaches saturation, existing load may be displaced
from a selected processing window and new loads may be deferred
from the system. These deferred loads can have a profound effect
on a system after the bottleneck is removed. Consider the paradox
of a 25% upgrade... we were 100% busy before the upgrade and 120%
after... where did the upgrade go? You may have experienced this