Hey HN! We are happy to share Perforator – our internal cluster-wide profiler with great support for native languages and a built-in AutoFDO pipeline to simplify sPGO builds. Perforator allows you to profile most binaries without having to recompile or adjust the build process. We use it at Yandex to profile each pod inside a large cluster at modest speed (99Hz), collecting petabytes of profiles every day.<p>There's a blog post about it at <a href="https://medium.com/yandex/yandexs-high-performance-profiler-is-now-open-source-95e291df9d18" rel="nofollow">https://medium.com/yandex/yandexs-high-performance-profiler-...</a>.<p>Inspired by Google-Wide Profiling, we started continuous profiling years ago with simple tools like poormansprofiler.org. With the rise of eBPF, we came up with a simple and elegant solution providing detailed profiles without noticeable overhead. Pretty wild when you can see the guts of your production binaries in a flamegraph without them even noticing.<p>Some technical details:<p>- Our main contribution is infrastructure for continuous PGO using AutoFDO. Google and Meta have done tremendous work on building PGO infrastructure, and we made the last missing piece of the puzzle to make this work well and scalable.<p>- Native binaries are profiled through eh_frame analysis, interpreted/JIT-compiled languages are profiled through perf-pid.map or hardcoded structure offsets.<p>- We render profiles in multiple ways, the most common one is a fast implementation of FlameGraphs, rendering 1M frames in 100ms.<p>- We provide Helm charts to easily deploy Perforator on your k8s cluster.<p>- You can use Perforator in standalone mode as a replacement for perf record.<p>I'd love to answer your questions about the tool!