<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>High-Performance on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/high-performance/</link>
    <description>Recent content in High-Performance 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/high-performance/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Memory Allocators: jemalloc vs tcmalloc vs mimalloc for Production Servers</title>
      <link>https://www.pistack.xyz/posts/2026-06-02-memory-allocators-jemalloc-tcmalloc-mimalloc-guide/</link>
      <pubDate>Tue, 02 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-02-memory-allocators-jemalloc-tcmalloc-mimalloc-guide/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;When running production workloads on Linux servers, the default glibc &lt;code&gt;malloc&lt;/code&gt; implementation often becomes a bottleneck. Database engines, web servers, caching systems, and high-throughput applications can see dramatic performance improvements — often 10-30% — simply by switching the memory allocator. This article compares three battle-tested alternatives: &lt;strong&gt;jemalloc&lt;/strong&gt;, &lt;strong&gt;tcmalloc&lt;/strong&gt;, and &lt;strong&gt;mimalloc&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
