wspy – added topdown memory analysis
As a followup to a previous post, I’ve added support to wspy for topdown analysis for backend stalls.
Continue reading →mev
Investigating Intel performance counters for backend memory costing…
I’ve implemented the first level for topdown performance counter analysis and also done an initial analysis of ~15 workloads from recent Phoronix article. A logical next step is to expand the “backend bound” category to first separate CPU-bound vs. memory-bound … Continue reading →
Off CPU analysis, getrusage, wait4 and related techniques…
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 →
wspy – process tracing, lost nodes and potential refactoring
One of the tough bugs I’ve noticed sometimes pop up is an “orphaned” process tree in my tree. When I’ve collected trees of processes, very occasionally I’ll have a tree node drop on the floor and show up as an … Continue reading →
Set up Ryzen 7 1700 system
I have set up a Ryzen 7 1700 system. I bought it at Costco at point it was discounted at point the older CPUs are getting discounted in time for newer.
Continue reading →Phoronix benchmarks – new Ryzen processors; looking @ the workloads
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 →
Investigating performance counters related to memory
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 →wspy – added csv file as well as analysis functions
I have updated wspy to dump a “processtable.csv” file at the same time it dumps a “processtable.txt” file. This gives me several advantages: I’ve separated the format of output from collecting instrumentation. Hence, I can run things once to collect … Continue reading →
Top down performance counter analysis (part 3) – wspy
As described in top down performance counter analysis part 1, top down analysis is an approach that uses key performance counters to characterize an application and then successively drills down with further refinement. On Intel x86 processors, this first level … Continue reading →
Top down performance counter analysis (part 2) – wspy
As described in top down performance counter analysis part 1, top down analysis is an approach that uses key performance counters to characterize an application and then successively drills down with further refinement. On Intel x86 processors, this first level … Continue reading →