Skip to main content

Use Case 1: PFBuilder on SPEC CPU2017 Benchmark

Take the example of monitoring PFBuilder output when SPEC CPU2017 649.fotonik3d_s accesses CXL memory.

Steps:

  1. Use numactl to control the app to access CXL memory:
       sudo numactl --membind=4 bin/runcpu --config=config 649.fotonik3d_s

  1. Use online mode to observe PFBuilder output during app execution, and store it in InfluxDB under the name 649.fotonik3d_s.

  2. To view aggregated PFBuilder output on all paths and components:

       python3.8 main.py monitor -app "sudo numactl --physcpubind=32 --membind=4 path/to/SPEC/bin/runcpu --config=path/to/SPEC/config 649.fotonik3d_s" -online build -time 5 -savename 649.fotonik3d_s -path DRd,RFO,HWPF,DWr,LD,ST -pmu default
  1. To view PFBuilder output on DRd path for specific core32 components:
       python3.8 main.py monitor -app "sudo numactl --physcpubind=32 --membind=4 path/to/SPEC/bin/runcpu --config=path/to/SPEC/config 649.fotonik3d_s" -online build -time 5 -savename 649.fotonik3d_s -path DRd -pmu core32-SB,core32-L1D,core32-LFB,core32-L2