<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Goroutine-Pool on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/goroutine-pool/</link>
    <description>Recent content in Goroutine-Pool on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 19 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/goroutine-pool/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Object Pool Libraries in Go: ants vs pond vs bytebufferpool vs conc</title>
      <link>https://www.pistack.xyz/posts/2026-06-19-self-hosted-go-object-pool-libraries-ants-pond-bytebufferpool-conc/</link>
      <pubDate>Fri, 19 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-19-self-hosted-go-object-pool-libraries-ants-pond-bytebufferpool-conc/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Go&amp;rsquo;s goroutines are lightweight, but spawning thousands of them without bounds can still exhaust memory and degrade performance. Object pool libraries solve this by pre-allocating resources and reusing them — reducing GC pressure, bounding concurrency, and improving throughput in self-hosted Go services.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
