https://master--suspicious-stonebraker-7d2d21.netlify.app/tags/profilers/ Recent content in Profilers on Nikhil's blog Hugo -- gohugo.io en-US Sat, 24 Nov 2018 14:05:00 -0700 https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2018/sampling-profiler-internals-suspending-threads/ Sat, 24 Nov 2018 14:05:00 -0700 https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2018/sampling-profiler-internals-suspending-threads/ This is part 2 of the Sampling Profilers Internals series. Introduction Suspending threads Stack unwinding Symbolication Presenting profile output Extending the profiler to managed languages As described in the introduction, a sampling profiler captures the stack of each thread every few milliseconds. To do this, it is preferable to suspend the thread 1. We don’t want the stack changing under us as we are profiling. Even worse, a thread could just terminate while we were attempting to profile it and invalidate all the memory we want to read. https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2018/sampling-profiler-internals-introduction/ Sat, 24 Nov 2018 14:00:00 -0700 https://master--suspicious-stonebraker-7d2d21.netlify.app/post/2018/sampling-profiler-internals-introduction/ Sampling profilers are useful tools for performance analysis of programs. I’ve spent a lot of time over the past several months digging into various implementations of sampling profilers and reading a lot about symbolication, threads, stack unwinding and other gory operating system details. This series of posts attempts to summarize my understanding. Introduction Suspending threads Stack unwinding Symbolication Presenting profile output Extending the profiler to managed languages Background High CPU usage is a problem that comes up often in widely used software.