wspy – followup: support for ptrace as well as ftrace
As a followup to my post about ptrace vs ftrace I have added a basic ptrace support to wspy.
Continue reading →As a followup to my post about ptrace vs ftrace I have added a basic ptrace support to wspy.
Continue reading →While the names sound different, ptrace and ftrace are two rather different methods of implementing process instrumentation.
Continue reading →I have enhanced wspy to add –set-counters option.
Continue reading →Added a new option to wspy to get the performance counters from the linux kernel. This builds on my previous learnings to inventory the system and build counter information provided by the system including event numbers, umasks and other fields.
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 →There was an article posted on phoronix comparing several Linux servers including POWER9, Intel and AMD EPYX. Analysis for this article was minimal; so in this post I dug in a bit more on characteristics of the benchmarks of what … 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 →
I have now enhanced wspy to add an option for –diskstats. This option samples, /sys/block/*/stat files to save away disk read and write statistics. The same information is also reported in /proc/diskstats. Another option added at same time is –set-cpumask … Continue reading →