014 Reviewing Metrics and Logging Data Using Performance Co-Pilot Part 2 Study Guide
014 Reviewing Metrics and Logging Data Using Performance Co-Pilot Part 2 Study Guide
Mike Bunch
LINUX TRAINING ARCHITECT
REVIEWING METRICS AND LOGGING DATA USING PERFORMANCE COPILOT
Lesson Objective
Review and demonstrate various Performance Co-Pilot tools (e.g., pminfo, pcp atop, and pcp
mpstat) and use them to view various system metrics.
Lesson Notes
Performance Co-Pilot (PCP)
PCP was developed by Silicon Graphics (SGI and first included in RHEL 6.6. It has become the
preferred performance metrics analysis tool due to its ability to manage metrics for local and
remote systems as well as being highly configurable.
The sysstat tools (e.g., iostat and vmstat) are well know among Linux System
Administrators. PCP offers similar tools for a familiar experience.
Sysstat does not have a management service, relying on cron for repeating data collection,
limiting the collection intervals unless complex scripts are used while PCP operates as a systems
service, allowing for more flexibility for data collection and intervals.
REVIEWING METRICS AND LOGGING DATA USING PERFORMANCE COPILOT
NOTE This is not an all inclusive list, just a few examples for comparison.
REVIEWING METRICS AND LOGGING DATA USING PERFORMANCE COPILOT
# Monitor CPU load, memory usage, and disk write operations per partition:
pmdumptext -Xlimu -t 2sec 'kernel.all.load[1]' mem.util.used
disk.partitions.write -h localhost
# Review CPU load, memory usage, and disk write operations from an archive:
pmdumptext -Xlimu -t 2sec 'kernel.all.load[1]' mem.util.used
disk.partitions.write -a archive_name