Performance management is a key consideration on any platform.  A system may have several resources (CPU, I/O, storage, network etc.) that collectively work together to process a workload. To assess overall health of the system, mainframe system reports can be reviewed on certain key performance metrics on these resources. These metrics are measured and compared against the service level agreements (SLA), or performance Rule-of-Thumb standards.

An SLA is a contract between the user and system that describes the goals to meet for business critical workloads. If results are not as expected, then mission critical workloads running on the system will usually suffer.  Some of the possible remedies could be: performance tuning to get metrics results to base standards, buy more resources, offload eligible workloads to specialty engines, or steal from less critical work by adjusting priorities.

Types of workloads

First let’s take a look at typical workloads that run on mainframe systems. They can be classified into 2 flavors – Batch processing or Online transactional processing.

Batch workloads: Batch workloads process high volumes of data, and produce outputs/reports, are typically scheduled programs processed without user interaction, and are often run during off-peak hours. As an example, a mainframe job that requests large numbers of customer billing statements or customer orders etc.

Transactional workloads: These workloads typically involve end user interactions. Transactions are usually short and are often considered mission-critical workloads for the business. Examples are: bank ATM transactions, merchant credit card processing at checkout stations, online order purchase, etc.

Performance metrics

Mainframe systems regularly capture key systems metrics to gauge system performance, data that various performance monitoring tools use to display to end users. Here are some of them:

Average throughput
This indicates the average number of service completions per unit time. For example, the number of transactions per second or minute. Transaction workloads are typically measured using this performance metric.

Average response time
This measures the average amount of time it takes to complete a single service. Transactional workloads are usually measured using this performance metric – it can also be specified as an SLA goal for workloads.

Resource utilization
Typically, this metric shows the amount of time the workloads (batch or transaction) consumed resources over a period of time. Examples: CPU utilization, Processor storage utilization, I/O rates, paging rates etc.

Resource velocity
Velocity is a measure of resource contention. When multiple workloads require a resource (example CPU) at the same time then there is contention for the resource. While one workload is using the resource other workloads are put in a waiting queue. Resource velocity is the ratio of time taken for using the resource (A) to the total time spent using resource (A) and waiting in the queue (B). i.e., A / (A+B). This value is expressed as percentage of 0-100 range. A value of 0 means a high amount of contention for resource, and a value of 100 indicates no contention. This metric can be specified as an SLA goal for workloads.

Performance Index
As part of SLA, workloads are classified as service classes and each service class has goals. Goals for workloads can be expressed as response time, velocity, etc. Since there are several types of goals defined for various workloads in SLA, to determine how workloads are performing with respect to their defined goals, a simple metric performance index(PI) is used. PI is simply a ratio of defined goal vs achieved goal. A PI value of 1 means workloads are meeting goals. A value < 1 means workloads are exceeding the goals, and value > 1 means workloads are missing goals.

Hemanth Rama

Hemanth Rama

Senior Software Engineer at BMC Software
Hemanth Rama is a senior software engineer at BMC Software. He has 11+ years of working experience in IT. He holds 1 patent and 2 pending patent applications. He works on BMC Mainview for z/OS, CMF Monitor, Sysprog Services product lines and has lead several projects. More recently he is working on Intelligent Capping for zEnterprise (iCap) product which optimizes MLC cost. He holds master degree in computer science from Northern Illinois University. He writes regularly on LinkedIn pulse, BMC communities and his personal blog.
Hemanth Rama

Latest posts by Hemanth Rama (see all)

Share this article: Share on Facebook2Share on Google+1Tweet about this on Twitter0Share on LinkedIn16Email this to someone

Leave a reply

Your email address will not be published. Required fields are marked *