<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pyroscope on 黄文卓 | DevOps Engineer</title><link>https://socake.github.io/tags/pyroscope/</link><description>Recent content in Pyroscope on 黄文卓 | DevOps Engineer</description><generator>Hugo -- gohugo.io</generator><language>zh-CN</language><managingEditor>17691281867@163.com (Wenzhuo Huang)</managingEditor><webMaster>17691281867@163.com (Wenzhuo Huang)</webMaster><copyright>© 2026 Wenzhuo Huang</copyright><lastBuildDate>Sun, 12 Apr 2026 14:00:00 +0800</lastBuildDate><atom:link href="https://socake.github.io/tags/pyroscope/index.xml" rel="self" type="application/rss+xml"/><item><title>Linux 火焰图实战：从采集到定位问题</title><link>https://socake.github.io/posts/linux-flame-graph-practice/</link><pubDate>Sun, 12 Apr 2026 14:00:00 +0800</pubDate><author>17691281867@163.com (Wenzhuo Huang)</author><guid>https://socake.github.io/posts/linux-flame-graph-practice/</guid><description>CPU 飙高、响应慢、内存泄漏——这三类问题用火焰图都能快速定位。本文从怎么读火焰图开始，讲到 perf、async-profiler、py-spy 各自的适用场景，最后用一个真实的 Go 服务案例走完完整排查流程。</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://socake.github.io/posts/linux-flame-graph-practice/featured.jpg"/></item><item><title>Pyroscope 持续性能剖析生产实战：给每一行代码一个性能画像</title><link>https://socake.github.io/posts/pyroscope-continuous-profiling/</link><pubDate>Wed, 02 Jul 2025 10:00:00 +0800</pubDate><author>17691281867@163.com (Wenzhuo Huang)</author><guid>https://socake.github.io/posts/pyroscope-continuous-profiling/</guid><description>为什么 metrics/logs/traces 之外还需要 profiling，它解决的是什么问题，Pyroscope 的架构是什么，怎样以 2%~5% overhead 把它铺到整个 K8s 集群。</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://socake.github.io/posts/pyroscope-continuous-profiling/featured.jpg"/></item></channel></rss>