Log backtraces at obfuscated Android methods
Logging a stack trace is a useful way to tell why a method is being called. But
it's not always so easy to log a backtrace.
Tools like dtrace and linux-perf
Book Review: The Unicorn Project
These are my notes from Gene Kim’s book The Unicorn Project: A Novel about
Digital Disruption, Developers, and Overthrowing the Ancient Powerful Order
[https://booko.com.au/9781942788768/The-Unicorn-Project-A-Novel-about-Digital-Disruption-Redshirts-and-Overthrowing-the-Ancient-Powerful-Order]
. I enjoyed this
pprof -tagroot: Custom Labels in Go Flamegraphs
pprof -tagroot lets you break down & visualise pprof software profiles by custom, domain-specific key-value pairs (Labels, aka Tags) attached to each stack sample.
Profilerpedia: A map of the Software Profiling Ecosystem
I mapped out over 100 Profilers, what Profile Data Formats they output, and what Profiler UIs can visualise those formats: Profilerpedia
Attributing Latency in Go with Pprof Tags
A latency analysis of a Go program (Hugo), starting with in-app wall-clock
counters, then pprof CPU profiling, then adding custom dimensions to slice the
profile.
Background
I recently migrated Graphviz's docs