<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cpu-Affinity on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/cpu-affinity/</link>
    <description>Recent content in Cpu-Affinity on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 23 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/cpu-affinity/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Linux CPU Affinity Management: taskset vs numactl vs cset</title>
      <link>https://www.pistack.xyz/posts/2026-05-23-self-hosted-linux-cpu-affinity-management-taskset-numactl-cset-guide/</link>
      <pubDate>Sat, 23 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-23-self-hosted-linux-cpu-affinity-management-taskset-numactl-cset-guide/</guid>
      <description>&lt;p&gt;CPU affinity controls which processor cores execute specific processes on a Linux system. On multi-core servers running database engines, web servers, or real-time applications, improper CPU affinity can cause cache thrashing, NUMA penalties, and unpredictable latency. This guide compares three tools for managing CPU affinity on self-hosted Linux servers: &lt;strong&gt;taskset&lt;/strong&gt; (process-level pinning), &lt;strong&gt;numactl&lt;/strong&gt; (NUMA-aware placement), and &lt;strong&gt;cset&lt;/strong&gt; (advanced CPU set management with shielding).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
