<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Worker-Threads on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/worker-threads/</link>
    <description>Recent content in Worker-Threads on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 20 Aug 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/worker-threads/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Piscina vs Workerpool vs Poolifier in 2026: Which Node.js Worker Pool Should You Use?</title>
      <link>https://www.pistack.xyz/posts/2026-08-20-nodejs-worker-pools-piscina-workerpool-poolifier-comparison/</link>
      <pubDate>Thu, 20 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-08-20-nodejs-worker-pools-piscina-workerpool-poolifier-comparison/</guid>
      <description>&lt;p&gt;A single JSON serialization pass over 100,000 records blocks your Node.js event loop for &lt;strong&gt;300–800 milliseconds&lt;/strong&gt; — invisible in development, catastrophic at 5,000 requests per second. The standard fix is &lt;code&gt;worker_threads&lt;/code&gt;, but raw threads are a footgun: you manage lifecycle, queueing, and backpressure yourself. Three mature pools wrap this for you: &lt;strong&gt;Piscina&lt;/strong&gt;, &lt;strong&gt;workerpool&lt;/strong&gt;, and &lt;strong&gt;poolifier&lt;/strong&gt;. They look similar at a glance and differ sharply in API philosophy, runtime support, and deployment model. Here is what actually changes your choice in 2026.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
