<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Prathap's blog</title><link>https://example.org/</link><description>Recent content on Prathap's blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 29 May 2026 21:36:39 +0530</lastBuildDate><atom:link href="https://example.org/index.xml" rel="self" type="application/rss+xml"/><item><title>Achieving high write throughput - LSM Trees</title><link>https://example.org/blog/acheiving-high-write-throughput-lsm-trees/</link><pubDate>Fri, 29 May 2026 21:36:39 +0530</pubDate><guid>https://example.org/blog/acheiving-high-write-throughput-lsm-trees/</guid><description>&lt;p&gt;Imagine you are designing a system where there would be 100k writes/sec. Using Postgres or MySQL to store the events would be slow because under the hood, they use B-trees. B-trees maintain data in sorted order. So every write has to land at a specific position in the tree. This means each write is essentially a random I/O operation (you have to seek to the right leaf page on disk). Random I/O is significantly slower than sequential I/O, even on SSDs. Moreover, when a leaf page fills up, it has to split and the parent node has to be updated to point to the new pages. This can cascade up the tree, causing multiple disk writes for what was a single logical write. Enough about B trees for now, I&amp;rsquo;ll cover B-trees in detail in a future blog.&lt;/p&gt;</description></item><item><title>Garbage Collection In Go</title><link>https://example.org/blog/garbage-collection-in-go/</link><pubDate>Thu, 19 Feb 2026 21:36:39 +0530</pubDate><guid>https://example.org/blog/garbage-collection-in-go/</guid><description>&lt;p&gt;Being a self-taught developer without a formal education in CS, I have always wondered where the program that I&amp;rsquo;m running stores my variables. I got to know the answer to that when I started learning &lt;strong&gt;Mastering Go&lt;/strong&gt; by &lt;a href="https://github.com/mactsouk"&gt;Mihalis Tsoukalos&lt;/a&gt;. In this blog, I&amp;rsquo;ll try to cover garbage collection in Golang from a beginner&amp;rsquo;s perspective.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="what-is-garbage-collection"&gt;What is Garbage Collection?&lt;/h2&gt;
&lt;p&gt;In the literal sense, it means to clear off the memory that is no longer in use. But wait. What is the memory that we are talking about? Where exactly is this memory located at?&lt;/p&gt;</description></item></channel></rss>