Phoronix posted an an article measuring Ryzen 2600 and Ryzen 2700. The comparisons were a 9-way CPU comparison of new processors (7 AMD and 2 Intel). In this posting, I’ll look more at the workloads being tested.
Continue reading →After my previous post on backend analysis, I got a chance to look further breaking out backend stall statistics.
Continue reading →Phoronix posted an article about Clear linux. The goal was to look for changes in the system after all packages were rebuilt with GCC 8.1.
Continue reading →Phoronix posted an article benchmarking GCC 8.1 today. These benchmarks compare GCC 8.1 vs GCC 7.3 on a variety of Ubuntu 18.04 systems. While I haven’t reproduced the exact comparisons on Ubuntu, in this article I make some notes about … Continue reading →
Phoronix posted an article about Clear linux benchmarks. The article was a three-way comparison between Clear Linux, Ubuntu 18.04 LTS and Fedora 28 on a variety of workloads. While I don’t have the same systems to compare, this posting characterizes … Continue reading →
On May 2nd, Phoronix published a benchmark comparison of 18.04 vs. 16.04 on multiple systems. It was intended to compare “out of the box” experiences. As the article notes, similarities and differences between these systems include gcc 7.3 vs. gcc … Continue reading →
As April finished, useful to take stock of where analysis is at as well as next steps. During May, I may also take a few week break to finish publishing my book and a cycle trip- so also useful to … 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 →I have added a new mode: –perfcounter-model application this supplements the previous two modes: –perfcounter-model process –perfcounter-model core This mode works similar to the process model, except only the root process is instrumented and then the “inherit” flag is passed. … Continue reading →
The ptrace(2) man page shows how one can subscribe for events such as PTRACE_EVENT_FORK or PTRACE_EVENT_VFORK type events that happens when a process calls fork()/vfork(). At such an event one can then call ptrace(PTRACE_GETEVENTMSG,…) to retrieve the pid of the … Continue reading →