<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Kubernetes Performance Engineering on Nubis Morocco</title>
    <link>https://nubis.ma/series/kubernetes-performance-engineering/</link>
    <description>Recent content in Kubernetes Performance Engineering on Nubis Morocco</description>
    <generator>Hugo -- 0.148.1</generator>
    <language>en</language>
    <lastBuildDate>Mon, 25 May 2026 22:30:24 +0200</lastBuildDate>
    <atom:link href="https://nubis.ma/series/kubernetes-performance-engineering/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A Practical Guide to NUMA Affinity in Kubernetes</title>
      <link>https://nubis.ma/blog/a_practical_guide_to_numa_affinity_in_kubernetes/</link>
      <pubDate>Sun, 22 Feb 2026 10:00:00 +0000</pubDate>
      <guid>https://nubis.ma/blog/a_practical_guide_to_numa_affinity_in_kubernetes/</guid>
      <description>&lt;p&gt;NUMA effects are one of those problems that don’t show up in dashboards, but will happily show up in your p99 latency and in “why is this box slower than the identical box next to it?”&lt;/p&gt;
&lt;p&gt;Kubernetes can help—but only if you enable the right node-level managers and verify the result from inside the workload.&lt;/p&gt;
&lt;h3 id=&#34;what-is-numa&#34;&gt;What is NUMA?&lt;/h3&gt;
&lt;p&gt;Modern multi-socket servers split memory banks across CPU sockets. Each socket and its directly attached memory form a &lt;strong&gt;NUMA node&lt;/strong&gt; (Non-Uniform Memory Access). Accessing memory on your own socket is fast (local); crossing the interconnect to another socket’s memory is slower (remote).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
