trace-cmd and kernelshark
Found a new tool for creating and browsing kernel ftrace events.
Continue reading →Found a new tool for creating and browsing kernel ftrace events.
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 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 →
I have enhanced wspy to read performance counters. It now has three different instrumentation methods: Reading ftrace logfiles from kernel subsystem. Currently reads the scheduler events for fork/exec/exit to construct process trees Reading /proc/stat on periodic basis (once per second) … Continue reading →
Two improvements have been added to the wspy program: Added a -z option that creates a zip archive with data files related to the wspy run Added a script that calls gnuplot to plot CPU usage over time. Below is … Continue reading →
Another useful tool from the likwid performance monitoring and benchmarking suite is likwid-topology. Provides thread (hyperthread), cache (L1, L2, L3) and NUMA (memory) topology together. Output below shows my i7-4770S CPU is a 4-core hyperthreaded processor with a 32KB L1D … Continue reading →
Created a simple monitoring tool named wspy for workload spy. Source is hosted at http://www.github.com/mvermeulen/wspy This is a wrapper program that collects data as the program runs. The initial program has two data collectors: trace – which uses the ftrace … Continue reading →