Powr System Benchmark

Performance Management
for Power Systems:

Interactive Graphing Support for IBM i
http://www.ibm.com/systems/power/support/perfmgmt/
PM_i_int_Tour_July_2012.ppt
© 2010 IBM Corporation
1
IBM Global Technology Services
Management
Summary
Graphs
The Management Summary Graphs are available for

servers/LPARs that are entitled at the summary / No
Additional Charge level.
Entitlement is earned when the system is using IBM
Electronic Service Agent or an IBM management
console with the call home function enabled in a
Power Systems environment
2 © 2010 IBM Corporation
All entitled graphs are accessible by the end user customer via secure IBM Internet ID and password.
End users are provided a ‘registration’ key when the server or partition first transmits data.
Visit the PM Getting Started tour on the PM for Power Systems home page for more information.
http://www.ibm.com/systems/power/support/perfmgmt
2
Management Summary Graphs (partition view)
Management Summary Graphs

These graphs are available at no additional charge providing the system is using IBM
Electronic Service Agent and / or an IBM management console with the call home functions
enabled in a Power Systems environment.
PM for Power Systems graphs are at the partition level, not at the total system level (unless
there is no partitioning on the system).
This graphic uses the colors to indicate the current status of the resource and the projected
status for the next 12 months.
•Green bar – resource utilization is within good performance guidelines
•Yellow bar – resource utilization is marginal, you may be experiencing intermittent
performance degradation due to the resource
•Red bar – resource utilization is critical, the resource utilization is beyond the guidelines for
good performance and corrective action should be taken.
For more information on all graphs, visit the PM for Power Systems Graph Reference
Document on the PM home page at http://www.ibm.com/systems/power/support/perfmgmt
3
Full Function
Interactive
Reports
The following reports are available for servers/LPARs

that are entitled at the Full Function level of PM for
Power Systems.
Contact IBM or and IBM Business Partner for terms
and conditions in your country.
The Full Function detailed reports available from PM for Power Systems are packaged differently by country.
Contact your local IBM Representative or an IBM Business Partner for more information.
PM for Power Systems graphs default at the partition level, not at the total system level (unless there is no
partitioning on the system). Full system views and physical processor views are available if the customer is
subscribed to the Full Function detail reports and special set up instructions are implemented.
Additional country contact information is available on the ‘contacts’ page at the main PM for Power Systems
home page
For more information on all graphs, visit the PM for Power Systems Graph Reference Document on the PM
home page at
4
Interactive graphing
 Detailed reports are available on most graphs with the full function
option of PM for Power Systems (and on the Management
Summary graph which is entitled with the no additional charge
offering).
 You are able to view monthly, daily, and hourly level reports.
 At the hourly level, you can customize a graph view down to a

single day.
 The following graphs are examples of the reports that are

available. You will notice that in many cases the performance
guidelines are depicted on the graph.
5
Guidelines for total processor utilization
These thresholds determine whether a resource is within guideline, marginal

or critical in the following processor utilization reports.
These are the processor utilization guidelines. They are based on the number of processors that are configured
for the server/LPAR.
These are the thresholds that trigger whether a constraint is normal, marginal or critical.
6
Total ‘System View’ – Configuration
A view of the total available processors on the system and how they are allocated
The System Configuration Graph provides an overview of the total

cores on the system and how they are allocated.
The number of ‘activated’ cores represents the number of cores that

can be used. The ‘Total Cores’ represents the number of cores shipped
with the system. The difference between the ‘total cores’ and the
‘activated cores’ represents the Capacity on Demand cores available for
growth purposes.
The second horizontal bar represents how the activated cores are
allocated.
7
Total ‘System View’ – Monthly Graph (#1)
A 13 month total system view of utilization versus allocated and capacity on demand processors
The System View – Peak Total Processor Utilization – with Trend

Projection graph portrays the entire system’s peak average utilization
(black diamond) against available activated (see green shade)
processor cores. A perspective of remaining available processors (see
purple shade above) on the system is shown through the Capacity on
Demand processors.
The columns with no data reflect months where PM data was not
collected.
The left hand scale shows total combined processor seconds available
per hour based the respective number of cores (right hand scale).
The right hand three columns reflect projected growth or decline in

utilization over the next 3 months based on the last 3, 6 and 12 month
history.
The 13 month trend provides perspective on total system utilization

trends against total system capacity.
8
Total ‘System View’ – Monthly Graph (#2)
A view of total system utilization versus allocated processors for the last 13 months
The System View – Peak Active Processor Utilization – with Trend

Projection graph provides a 13 month view of peak average utilization
as shown against total capacity of the activated processors and
partitions on the system.
The height of the bar reflects the total activated processors for the
month.
The green, yellow and red color coding reflects performance utilization
thresholds for good (green), cautionary (yellow) or needs immediate
attention (red). These target thresholds vary based on the total number
of processors activated on the system.
The black diamond’s position in relation to the ‘green / yellow / red’

threshold colors indicates the status of current performance.
The right hand three columns reflect projected growth or decline in

utilization over the next 3 months based on the last 3, 6 and 12 month
history.
9
Total ‘System View’ – Daily Graph
A combined view by day of all processors / partitions on the system
The System View – Processor Utilization Per Day During the Period
graph combines all the partitions on the system to show both a
combined processor seconds perspective (left hand legend) and
combined core perspective (right hand legend) of overall system
utilization at a daily interval.
The left hand scale shows the processor seconds per hour in thousands
for the respective number of cores (the right hand scale).
Both the ‘average per day’ (average for the shift) and ‘peak average’
(average for the 2 busiest hours during the shift) are shown.
The ‘max usage’ red line indicates the single greatest hourly usage
interval for the day.
The ‘blank’ days in the graph are a reflection of no PM data being

available for those days.
10
Total ‘System View’ – Hourly Graph
A combined view by hour of all processor / partition utilization on the system
The System View – Hourly Average During the Period provides a view
of combined processor utilization for the respective hour across all
partitions and cores.
The hours on the graph begin at 6:00 a.m.
The green shaded area reflects activated cores; the purple shaded area
reflects the number of cores remaining on the system for capacity on
demand expansion.
11
Shared Physical Processor Pool Peak Utilization – with Trend Projections
Shared Physical Processor Pool Peak Utilization – with Trend

Projections
This graph provides the combined utilization of all the processors in the
shared pool over the past year. The right hand three columns provide a
projection of utilization for the next three months based on the last 3,6
and 12 months history. (Note: the 6 and 12 month projected trend lines
are abnormally affected by the lack of data in this graph example.)
The ‘blank’ months in the graph indicate that no PM data was

transmitted for these months.
The number of Cores: Active = the number of cores on the total system.
The number of Cores: In Shared Pool = the number of cores assigned
to the pool.
The black diamond reflects the peak average usage for the respective
month. Peak average by definition is an average of the two busiest
hours of the day for the shift for the 30 day period.
The height of the ‘bar’ reflects the total resource assigned to the pool.
The change in pattern or color code indicates when the utilization would 12
Shared Physical Processor Pool Usage, per Day
Shared Physical Processor Pool Usage, per Day

This graph depicts peak average usage by day for all the combined
cores assigned to the shared pool.
The plotted line reflects the peak average usage for the respective day.
Peak average by definition is the two busiest hours of the day for the
shift.
The Cores: Active = the number of cores on the system. The Cores: In
Shared Pool = the number of cores assigned to the pool.
The right hand scale shows the maximum number of cores “In Shared
Pool” that were used at any one time during the period.
13
Shared Physical Processor Pool Average Usage, by Hour – During the Period
Shared Physical Processor Pool Average Usage, by Hour – During

the Period
This graph depicts an hourly view for the last 30 days of the combined
processor usage for all processors assigned to the pool.
The black diamond depicts the average processor usage for all priorities
(ie interactive, batch and System i) for the hour for the shift for the last
30 days. The solid line indicates the single hour maximum usage for
the respective hour of the day.
The Cores: Active = the number of cores on the system. The Cores: In
Shared Pool = the number of cores assigned to the pool.
The right hand scale shows the maximum number of cores “In Shared
Pool” that were used at any one time during the period.
14
Peak Processor Utilization, Total – with Trend Projections (partition view)
Peak Processor Utilization, Total

The Peak Processor Utilization graph shows the average total peak processor utilization per month for the last
13 months and it also provides you with a growth trend. It also shows you how the workload changes during a
year.
The symbols used on this graph are explained as follows:

• The forward slash (green) in the bottom of the graph shows the processor utilization that is acceptable.
• The cross-hatch (yellow) in the middle of the graph shows the processor utilization that is marginal.
• The backward slash (red) at the top of the graph shows the processor utilization that is critical.
• The black diamond shows the average of the two busiest hours per shift during the month. Actually, the black
diamond shows the size of the workload on the partition in CPW values. On the trend months, the pink diamond
shows the projected peak processor utilization based on the three last months utilization. The blue square
shows the projected peak processor utilization based on the last six months utilization. The yellow star shows
the projected peak processor utilization based on the last 12 months of utilization.
PM for Power Systems will depict the IBM i workload growth over time in CPWs. The advantage of plotting
CPWs is that it is a normalized unit of work independent of the resources allocated to the server/LPAR. This
means that the black diamonds on the graph represent the workload trend independent of the resources
allocated to the server/LPAR.
15
Peak Interactive Processor – with Trend Projections (partition view)
Peak Interactive Processor – with Trend Projections

The Peak Interactive Processor – with Trend Projections graph shows the average processor utilization for
interactive jobs (Job type = I) during the last thirteen months. It also shows the corresponding CPW value used
for the two busiest hours for the shift during the period.
The right hand three columns project growth for the next three months based on the previous 3, 6 and 12
month growth history.
The information under the Facts heading at the bottom of the graph outlines the recommended guidelines for
marginal and critical percentage.
16
Average Processor Utilization in % per Day

(partition view)
Average Processor Utilization in % per day

The Average Processor Utilization in % per Day graph shows the average processor utilization per measured
day during the period for three groups of priorities.
The symbols used on this graph are explained as follows:

• The forward slash (green) shows system usage (Jobtype = S).
• The cross-hatch (blue) shows interactive usage (Jobtype = I).
• The backward slash (red) shows the batch usage (Jobtype = B).
• The black line shows the average interactive work of the busiest single two hours during the shift for the
reported day, expressed as a percentage of total processor capability of the partition, (or total system if no
partitioning is used)..
•The left side of the graph shows the usage values in CPW and the right side shows the percentage.
17
Processor Utilization by Hour (partition view)
Processor Utilization by Hour

The Processor Utilization by Hour graph shows the hourly processor utilization average during the last 30-day
period. This allows you to see how the workload changes during a day.
• The time indication, 08 for example, represents the time range 08:00 through 08:59.
• The black line shows the busiest hour of interactive peak utilization for that hour during the last 30-day
period, expressed as a percentage of the total processor capability assigned to the partition. It is likely that
when this value is high, degraded response times were experienced during that hour on at least one day of the
period.
• The blue line shows the busiest hour of total peak processor utilization for that hour during the last 30-day
period. It is likely that your system experienced a degradation of throughput some day during the period, if this
percentage is high during a longer period.
• The red line shows the interactive limit that is defined in your system, set by the interactive feature installed,
the IBM i software Edition or set by the partition definition.
18
Memory: Percent of Time Faulting, Per Day / Per Hour (at partition level)
Percent of Time Faulting, Per Day

The Percent of Time Faulting, Per Day graph shows the time spent faulting in a percent for each day for the last
three months, or the period you choose. The information under the Facts heading at the bottom of the graph
outlines the recommended guidelines for marginal and critical percentage.
Percent of Time Faulting, Per Hour

The Percent of Time Faulting, Per Hour graph shows time spent faulting in percent per hour for the last month,
or the period you choose.
• The average of the hours is indicated by the forward slash (blue) column.
• The hour with the heaviest paging (peak) is indicated as a line (black).
• The straight (red) line is the guideline.
19
Peak Disk Arm Utilization in %, Utilization by Hour (at partition level)
Peak Disk Arm Utilization in %

This graph displays the average of the two peak hours for disk arm utilization, for each day during the last three
months, or the period you choose. The information under the Facts heading at the bottom of the graph states
the recommended guidelines for marginal and critical peak utilization and the months calculated to reach this
guideline with your percent usage.
Disk Arm Utilization by Hour

The Disk Arm Utilization by Hour graph shows the average disk arm utilization by hour per the last month, or
the month you select. The information under the Facts heading at the bottom of the graph states the
recommended guidelines for marginal and critical peak utilization.
Note for systems with SAN-based storage:

Each server/LPAR’s graph for disk arms will reflect utilization of the portion of the SAN which is accessed by
that server/LPAR. In rare cases, multiple servers using storage on the same SAN unit may result in a slight
increase in displayed disk arm utilization.
20
Peak Disk Arm Utilization in % - with Trend Projections

(at partition level)
Peak Disk Arm Utilization in % (3 Month Trend)

This graph shows the average peak disk arm utilization for up to 13 months, and a three-month trend projection
for the two busiest hours per measured day during the period. The trend projects the disk arm utilization for the
next three months based on the last 3, 6 and 12 months growth history. The trend months are the three last
months shown.
Because each displayed value is an average, the actual values during each month can be higher or lower than
what is indicated on the graph.
Note for systems with SAN-based storage:

Each server/LPAR’s graph for disk arms will reflect utilization of the portion of the SAN which is accessed by
that server/LPAR. In rare cases, multiple servers using storage on the same SAN unit may result in a slight
increase in displayed disk arm utilization.
21
Disk Space Usage in %, per Day / Trend Projection (at partition level)
Disk Space Usage in % per Day

The Disk Space Usage in % per Day graph shows the disk space utilization for the last three months or the
period you choose.
Disk Space Usage in %, - with Trend Projections

The Disk Space Usage in % - with Trend Projections graph shows the average disk space utilization for up to
13 months and a three month trend projection for space utilization based on the last 3, 6 and 12 month history.
The facts section displays the recommended guidelines for marginal and critical peak percentage. It also
indicates the number of months before this system reaches the guideline, the change in the amount of the
stored data and the maximum usage of disk space in percent during the period.
22
Communication Lines: Line Utilization (at partition level)
Line Utilization
The graph shows the average communication line utilization for the last three months for each communication
line while it is varied on during the collection period. Communication line errors show up in red.
Line utilization must be greater than one percent for the line to be shown in the graph.
23
Transactions: Volume per Hour, Daily / 3 Month Trend (at partition level)
Transaction Volume per Hour

In this graph, the thin blue line illustrates the average transaction volume per hour for each day during the last
three months. The thick red line shows the average transaction volume for the hour that had the most
transactions per day during the last three months.
Transaction Volume per Hour – History and 3 Month Trend

This graph shows the average number of transactions per hour over a period of 13 months. The trend for the
next three months is calculated based on this data.
A ‘Transaction’ is any type of interaction that causes an interaction with the system. This includes the Enter
Key, Command Key, page up and page down.
24
Transactions per Hour (at partition level)
Transactions per Hour

This graph shows the average number of transactions for all users per hour. You can chose up to 31 days
worth of data to display on this graph.
Under the Facts section, you see the average transaction characteristics for the current and previous two
months.
The characteristics are:
• CPU time in seconds
• Average number of I/Os
• Average number of synchronous I/Os
25
Average Number of I/O per Transaction / Processor Utilization for the Average
Transaction per Hour (at partition level)
Average Number of I/Os per Transaction

This graph shows the average number of I/Os per transaction for all users per hour. Both the total number of
I/Os per transaction and the number of synchronous I/Os per transaction are shown.
Processor Utilization for the Average Transaction per Hour

This graph shows the amount of processor time used per transaction.
26
Print outs - Daily Average per Hour (at partition level)
Print Outs - Daily Average per Hour

The graph shows the average number of pages per hour being submitted both interactively and in total.
The Top Ten reports show the top ten print jobs with the most pages and the top ten users printing the most
pages.
These reports all show the number of pages written to output queues. This might not be identical to the number
of pages printed to the printer. The difference in the number of pages can be attributed to the fact that output
queue jobs can be canceled, never printed, or printed multiple times.
27
Number of Jobs per Measured Day (at partition level)
Number of Jobs per Measured Day

This graph shows the number of active jobs per measured day during the period.
• An interactive job starts when a user signs on to the system and ends when the user signs off.
• A batch job begins when the job becomes active from the job queue.
28
Number of I/O’s for Batch Jobs / Processor Time per I/O for Batch Jobs
Number of I/O’s for Batch Jobs

This graph gives statistics about the I/O characteristics of an average batch job. The I/O sections show both
asynchronous I/O and synchronous I/O. An increase in the number of batch synchronous I/O over a time period
can indicate that:
• More batch work is being done.
• Work management settings of the partition are changed.
• An application has been changed.
Processor Time per I/O for Batch Jobs

This graph shows the average processor seconds per I/O for the batch jobs. An increase in batch job
processor utilization can result when jobs use more and more processor over time.
29
Response Time per Day / by the Hour (at partition level)
Average Response Time per Measured Day

This graph shows the internally measured IBM i response time in average for all the interactive jobs, for each
day, for the last three months.
Average Response Time by the Hour

This graph shows the internal IBM i average response time for all interactive jobs, for each hour.
30
Local: Response Time per Day / by the Hour (at partition level)

This graph shows the average response time for all users connected via 5250 type devices or devices that
emulate a 5250, for each day during the specified period.

This graph shows the average response time for all users connected via 5250 type devices or devices that
emulate a 5250, for each hour during the specified period.
31
PC: Response Time per Day / by the Hour (at partition level)

This graph shows the average response time for all PC users connected via SNA, for each day during the
specified period.

This graph shows the average response time for all PC users connected via SNA, for each hour during the
specified period.
32
Facts: Response Time (at partition level)
Response Time
The Response Time chart shows the 10 users with the longest combined response times in seconds during the
measured period.
Response Time - Average

The Response Time – Average chart shows the 10 users with the longest average response times in seconds
during the measured period.
33
Facts: Transaction Analysis (at partition level)
Transactions Volume
The Transactions Volume by user chart shows the 10 users with the most transactions per day during the
measured period.
Transaction Analysis – I/O

The Transaction Analysis - /Os by user chart shows the 10 users with the most I/Os per transaction in the
measured period.
Transaction Analysis – Processor Time

The Transaction Analysis – Processor Time chart shows the 10 users with the most processor time per
transaction in the measured period.
34
Facts: Batch Jobs (at partition level)
Batch Jobs – Processor Time

The Batch Jobs – Processor Time chart shows the 10 batch jobs with the most processor time per job during
the measured period.
Batch Jobs - I/Os

The Batch Jobs - I/Os chart shows the 10 batch jobs with the most I/Os per second during the measured
period.
Batch Jobs - Most Frequent

The Batch Jobs - Most Frequent chart shows the 10 batch jobs that run most frequently in the measured
period.
35
Print graphs
36
Facts: System Values / System Resources Summary
System Values report

The System Values report shows the values set for key performance values. Also shown are the actual
average active jobs and maximum active jobs. For best performance, adjust these values based on a regular
review of the actual jobs.
The values shown are:

• Active jobs
• Additional number of active jobs
• Total jobs
• Additional number of total jobs
• Performance adjustment
System Resources Summary

This chart lists the average, peak, and maximum values reported for each of the metrics during the selected
month, as well as the number of months remaining until each metric is predicted to reach its guideline.
37
For More Information
 See the Graph Reference Document at:

38

Powr System Benchmark

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Powr System Benchmark

Încărcat de

Drepturi de autor:

Formate disponibile

Performance Management

for Power Systems:

© 2010 IBM Corporation

The Management Summary Graphs are available for

2 © 2010 IBM Corporation

Management Summary Graphs (partition view)

3 © 2010 IBM Corporation

Management Summary Graphs

The following reports are available for servers/LPARs

 At the hourly level, you can customize a graph view down to a

 The following graphs are examples of the reports that are

5 © 2010 IBM Corporation

Guidelines for total processor utilization

These thresholds determine whether a resource is within guideline, marginal

6 © 2010 IBM Corporation

Total ‘System View’ – Configuration

7 © 2010 IBM Corporation

The System Configuration Graph provides an overview of the total

The number of ‘activated’ cores represents the number of cores that

Total ‘System View’ – Monthly Graph (#1)

8 © 2010 IBM Corporation

The System View – Peak Total Processor Utilization – with Trend

The right hand three columns reflect projected growth or decline in

The 13 month trend provides perspective on total system utilization

Total ‘System View’ – Monthly Graph (#2)

9 © 2010 IBM Corporation

The System View – Peak Active Processor Utilization – with Trend

The black diamond’s position in relation to the ‘green / yellow / red’

The right hand three columns reflect projected growth or decline in

Total ‘System View’ – Daily Graph

A combined view by day of all processors / partitions on the system

10 © 2010 IBM Corporation

The ‘blank’ days in the graph are a reflection of no PM data being

Total ‘System View’ – Hourly Graph

A combined view by hour of all processor / partition utilization on the system

11 © 2010 IBM Corporation

The hours on the graph begin at 6:00 a.m.

Shared Physical Processor Pool Peak Utilization – with Trend Projections

12 © 2010 IBM Corporation

Shared Physical Processor Pool Peak Utilization – with Trend

The ‘blank’ months in the graph indicate that no PM data was

Shared Physical Processor Pool Usage, per Day

13 © 2010 IBM Corporation

Shared Physical Processor Pool Usage, per Day

14 © 2010 IBM Corporation

Shared Physical Processor Pool Average Usage, by Hour – During

Peak Processor Utilization, Total – with Trend Projections (partition view)

15 © 2010 IBM Corporation

Peak Processor Utilization, Total

The symbols used on this graph are explained as follows:

Peak Interactive Processor – with Trend Projections (partition view)

16 © 2010 IBM Corporation

Peak Interactive Processor – with Trend Projections

Average Processor Utilization in % per Day

17 © 2010 IBM Corporation

Average Processor Utilization in % per day

The symbols used on this graph are explained as follows:

Processor Utilization by Hour (partition view)

18 © 2010 IBM Corporation

Processor Utilization by Hour

19 © 2010 IBM Corporation

Percent of Time Faulting, Per Day

Percent of Time Faulting, Per Hour