<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>性能调优 on 黄文卓 | DevOps Engineer</title>
    <link>https://socake.github.io/categories/%E6%80%A7%E8%83%BD%E8%B0%83%E4%BC%98/</link>
    <description>Recent content in 性能调优 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/categories/%E6%80%A7%E8%83%BD%E8%B0%83%E4%BC%98/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>bpftrace 实战：线上问题排查的瑞士军刀</title>
      <link>https://socake.github.io/posts/bpftrace-performance-debug/</link>
      <pubDate>Sun, 12 Apr 2026 10:00:00 +0800</pubDate>
      <author>17691281867@163.com (Wenzhuo Huang)</author>
      <guid>https://socake.github.io/posts/bpftrace-performance-debug/</guid>
      <description>strace 太重、perf 太原始、BCC 工具集要装一堆依赖——bpftrace 是这三者之间的平衡点。本文用四个真实场景讲清楚 bpftrace 的工作方式，帮你把它变成日常排查工具。</description>
      <media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://socake.github.io/posts/bpftrace-performance-debug/featured.jpg" />
    </item>
    
  </channel>
</rss>
