wspy – memory analysis for processes; need to sanity check the metrics…
As a followup to this post, I’ve implemented per-process capture of backend counters. I can now create a memory report from a process tree.
Continue reading →As a followup to this post, I’ve implemented per-process capture of backend counters. I can now create a memory report from a process tree.
Continue reading →As I looked to analyze x264, I saw that the On CPU metric was considerably less than other benchmarks like openssl or c-ray that are On CPU almost 100% of the time. I also noticed that my Ryzen 1700 box … Continue reading →
AMD released new Ryzen processors today. Phoronix published an article that benchmarked these processors. Anand Tech also published a review. TechReport also wrote a review. The posting is *not* measured on these new processors. Instead, it looks at dissecting the … Continue reading →
As part of my investigation to create a page for STREAM, I have tried to reconcile things with underlying performance counters. This page documents some of that work.
Continue reading →In this posting I summarize top-down performance counter analysis to evaluate workloads and show how this can be measured on Haswell using likwid-perfctr and perf. In part 2 to follow, I’ll describe how top down metrics have been added to … Continue reading →
I have found the counters necessary for wspy to get memory reads/writes. It wasn’t completely straightforward, so this documents the steps I took.
Continue reading →I kicked off a quick run through >100 Phoronix tests to get a quick profile and overall assessment, results from table below. A few items noted: Some of the tests didn’t run, most likely because they didn’t completely install or … Continue reading →
Kicked off a run with the Phoronix CPU suite using likwid-perfctr. Benchmarks that were single-threaded were pinned to a single CPU, others to all CPUs. #!/bin/bash likwid-perfctr -a | tail +3 | awk ‘{ print $1 }’ | while read … Continue reading →
As one of the first steps inpriming the pump for Phoronix benchmarks, I ran the wspy program on 21 candidate CPU benchmarks. My goal was to start with a rough characterization, e.g. single-threaded vs. multi-threaded or cpu-bound vs not. #!/bin/bash … Continue reading →
During a recent look at likwid-perfctr the performance counters didn’t look right in several aspects: CPU core to CPU core differences in what should be a symmetric benchmark and where wspy results showed processes balanced run to run differences with … Continue reading →