Siemens SM2 monitoring system 사용자 설명서
28
U3585-J-Z125-8-76
System monitoring
SM2 monitoring program
Bottleneck analysis
Before monitoring is started, you must clarify any performance problems, i.e. performance
expectations that are not satisfied. The following problems may exist:
expectations that are not satisfied. The following problems may exist:
●
System-oriented performance problems
These arise if the system throughput rate is unsatisfactory, and are indicated by a low
transaction rate and/or throughput rate. The most likely cause is the overloading of one
or more resources.
These arise if the system throughput rate is unsatisfactory, and are indicated by a low
transaction rate and/or throughput rate. The most likely cause is the overloading of one
or more resources.
●
User-oriented performance problems
These occur due to long delays when handling specific load requirements.
These occur due to long delays when handling specific load requirements.
The following monitored variables should be used to analyze bottlenecks. SM2 also allows
for more extensive analysis through addition monitoring programs.
for more extensive analysis through addition monitoring programs.
These monitored variables and monitoring programs make it easier to locate overloaded
resources:
resources:
The following settings are recommended for monitoring times (MODIFY-MEASUREMENT-
PERIODS statement):
PERIODS statement):
Monitoring must be carried out during peak load periods.
Due to the shorter monitoring cycle and the activated monitoring programs, bottleneck
analysis produces a large volume of data compared to trend monitoring. The volume of data
corresponds to the number of objects monitored and the number of events (DISK
monitoring program). The resulting SM2 output file may be very large.
analysis produces a large volume of data compared to trend monitoring. The volume of data
corresponds to the number of objects monitored and the number of events (DISK
monitoring program). The resulting SM2 output file may be very large.
Monitored variable
Monitoring program
Number of tasks in the system queues and at devices
Monitored by default
Number of input/output operations per device
Monitored by default
Working set per category
Monitored by default
CPU utilization and number of input/output operations per category
SYSSTAT
Number of input/output operations and volume of data transferred per
channel
channel
CHANNEL-IO
Access to catalog entries
CMS
Number of transactions
RESPONSETIME, BCAM-
CONNECTION, and UTM
CONNECTION, and UTM
Table 3: Monitoring programs used to locate overloaded resources
Sampling cycle (SAMPLING PERIOD):
400 milliseconds
Monitoring cycle (OFFLINE-PERIOD):
60 seconds
Analysis subinterval:
1 - 5 minutes
Monitoring period:
0.5 - 5 hours