<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Memory-Profiling on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/memory-profiling/</link>
    <description>Recent content in Memory-Profiling on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 02 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/memory-profiling/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux Memory Profiling: Memray vs Heaptrack vs Massif vs GPerfTools</title>
      <link>https://www.pistack.xyz/posts/2026-06-02-linux-memory-profiling-memray-heaptrack-massif-gperftools/</link>
      <pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-02-linux-memory-profiling-memray-heaptrack-massif-gperftools/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Memory leaks and excessive heap allocations are among the most common causes of server performance degradation. A production service that slowly consumes memory until OOM-killed, or a container that keeps restarting due to memory pressure — these problems require the right profiling tools to diagnose and fix. On Linux, several powerful open-source memory profilers help identify exactly where memory is being allocated, how long objects live, and where leaks originate.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
