<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Multiprocessing on Nalar</title>
    <link>https://nalar.dev/tags/multiprocessing/</link>
    <description>Recent content in Multiprocessing on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 09 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/multiprocessing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Stop Stuck Process Pools with Python 3.14</title>
      <link>https://nalar.dev/stop-stuck-process-pools-with-python-314/</link>
      <pubDate>Wed, 09 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/stop-stuck-process-pools-with-python-314/</guid>
      <description>&lt;p&gt;&lt;code&gt;ProcessPoolExecutor&lt;/code&gt; is a convenient way to spread CPU-bound Python work across multiple processes. Most of the time, its normal shutdown behavior is exactly what an application wants: stop accepting work, let running tasks finish, and clean up worker processes.&lt;/p&gt;&#xA;&lt;p&gt;Some failures do not fit that model.&lt;/p&gt;&#xA;&lt;p&gt;A worker can become stuck in native code, wait indefinitely on an external resource, or execute a task whose runtime has exceeded the application&amp;rsquo;s operational deadline. At that point, cancelling a &lt;code&gt;Future&lt;/code&gt; may not stop work that is already running, and waiting for an orderly pool shutdown may take too long.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
