PCM Tools | Building PCM | Downloading Pre-Compiled PCM | FAQ | API Documentation | Environment Variables | Compilation Options
Intel® Performance Counter Monitor (Intel® PCM) is an application programming interface (API) and a set of tools based on the API to monitor performance and energy metrics of Intel® Core™, Xeon®, Atom™ and Xeon Phi™ processors. PCM works on Linux, Windows, Mac OS X, FreeBSD, DragonFlyBSD and ChromeOS operating systems.
Github repository statistics: 
- Linux:
- Windows:
- FreeBSD:
- OS X:
- Docker container:
PCM provides a number of command-line utilities for real-time monitoring:
-
pcm : basic processor monitoring utility (instructions per cycle, core frequency (including Intel(r) Turbo Boost Technology), memory and Intel(r) Quick Path Interconnect bandwidth, local and remote memory bandwidth, cache misses, core and CPU package sleep C-state residency, core and CPU package thermal headroom, cache utilization, CPU and memory energy consumption)
-
pcm-sensor-server : pcm collector exposing metrics over http in JSON or Prometheus (exporter text based) format (how-to). Also available as a docker container. More info about Global PCM events is here.
-
pcm-memory : monitor memory bandwidth (per-channel and per-DRAM DIMM rank)
-
pcm-accel : monitor Intel® In-Memory Analytics Accelerator (Intel® IAA), Intel® Data Streaming Accelerator (Intel® DSA) and Intel® QuickAssist Technology (Intel® QAT) accelerators
-
pcm-latency : monitor L1 cache miss and DDR/PMM memory latency
-
pcm-pcie : monitor PCIe bandwidth per-socket
-
pcm-iio : monitor PCIe bandwidth per PCIe device
- pcm-numa : monitor local and remote memory accesses
- pcm-power : monitor sleep and energy states of processor, Intel(r) Quick Path Interconnect, DRAM memory, reasons of CPU frequency throttling and other energy-related metrics
- pcm-tsx: monitor performance metrics for Intel(r) Transactional Synchronization Extensions
- pcm-core and pmu-query: query and monitor arbitrary processor core events
- pcm-raw: program arbitrary core and uncore events by specifying raw register event ID encoding
- pcm-bw-histogram: collect memory bandwidth utilization histogram
Graphical front ends:
- pcm Grafana dashboard : front-end for Grafana (in scripts/grafana directory). Full Grafana Readme is here
- pcm-sensor : front-end for KDE KSysGuard
- pcm-service : front-end for Windows perfmon
There are also utilities for reading/writing model specific registers (pcm-msr), PCI configuration registers (pcm-pcicfg) and memory mapped registers (pcm-mmio) supported on Linux, Windows, Mac OS X and FreeBSD.
And finally a daemon that stores core, memory and QPI counters in shared memory that can be be accessed by non-root users.
Clone PCM repository with submodules:
git clone --recursive https://github.com/opcm/pcm.git
or clone the repository first, and then update submodules with:
git submodule update --init --recursive
Install cmake then:
mkdir build
cd build
cmake ..
cmake --build .
You will get all the utilities (pcm, pcm-memory, etc) in build/bin directory.
'--parallel' can be used for faster building:
cmake --build . --parallel
Debug is default on Windows. Specify config to build Release:
cmake --build . --config Release
On Windows and MacOs additional drivers are required. Please find instructions here: WINDOWS_HOWTO.md and MAC_HOWTO.txt.
FreeBSD/DragonFlyBSD-specific details can be found in FREEBSD_HOWTO.txt
- Linux:
- openSUSE:
sudo zypper install pcm - RHEL8.5 or later:
sudo dnf install pcm - Fedora:
sudo yum install pcm - RPMs and DEBs with the latest PCM version for RHEL/SLE/Ubuntu/Debian/openSUSE/etc distributions (binary and source) are available here
- openSUSE:
- Windows: download PCM binaries as appveyor build service artifacts and required Visual C++ Redistributable from www.microsoft.com. Additional drivers are needed, see WINDOWS_HOWTO.md.
- Docker: see instructions on how to use pcm-sensor-server pre-compiled container from docker hub.
PCM's frequently asked questions (FAQ) are located here.
PCM API documentation is embedded in the source code and can be generated into html format from source using Doxygen (www.doxygen.org).
The list of PCM environment variables is located here
The list of custom compilation options is located here
Packaging with CPack is supported on Debian and Redhat/SUSE system families. To create DEB of RPM package need to call cpack after building in build folder:
cd build
cpack
This creates package:
- "pcm-VERSION-Linux.deb" on Debian family systems;
- "pcm-VERSION-Linux.rpm" on Redhat/SUSE-family systems. Packages contain pcm-* binaries and required for usage opCode-* files.