<p>"Profiling in production with function call traces" - <a href="https://yosefk.com/blog/profiling-in-production-with-function-call-traces.html" target="_blank" rel="nofollow noopener" translate="no"><span class="invisible">https://</span><span class="ellipsis">yosefk.com/blog/profiling-in-p</span><span class="invisible">roduction-with-function-call-traces.html</span></a></p><p>super interesting and opinionated blog post! It argues for an ideally very cheap, but always on tracing profiler. the profiler keeps a ring buffer of a bunch of function entries and exit and saves it out on user-triggered events. can be used to produce a trace from a core dump, or to debug tail latency ('this event was extra slow? let's dump the ring buffer').</p><p>I want to try or reimplement this!</p>