<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Jemalloc on Tushar Choudhary</title><link>https://tushar-c23.github.io/tags/jemalloc/</link><description>Recent content in Jemalloc on Tushar Choudhary</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 14 Jun 2026 10:00:00 +0530</lastBuildDate><atom:link href="https://tushar-c23.github.io/tags/jemalloc/index.xml" rel="self" type="application/rss+xml"/><item><title>How jemalloc solves SMP — simplified</title><link>https://tushar-c23.github.io/posts/jemalloc_smp/</link><pubDate>Sun, 14 Jun 2026 10:00:00 +0530</pubDate><guid>https://tushar-c23.github.io/posts/jemalloc_smp/</guid><description>&lt;p&gt;Lately I&amp;rsquo;ve been going through Redis internals, trying to figure out how Redis works under the hood and implement the same brick by brick locally myself. During this I found out that Redis re-implements &lt;code&gt;malloc&lt;/code&gt; for its own use case, and further that Redis uses &lt;code&gt;jemalloc&lt;/code&gt; instead of &lt;code&gt;malloc&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;I got curious as to why? What &lt;code&gt;jemalloc&lt;/code&gt; was, what it does, and how it improves over our all-knowing classic &lt;code&gt;malloc&lt;/code&gt;.&lt;/p&gt;</description></item></channel></rss>