<?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>NUMA on Why did IT fail</title><link>https://www.why-did-it.fail/tags/numa/</link><description>Recent content in NUMA on Why did IT fail</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © 2026 Dominik Textoris (formerly Zorgnotti). All Rights Reserved.</copyright><lastBuildDate>Mon, 08 Jul 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://www.why-did-it.fail/tags/numa/index.xml" rel="self" type="application/rss+xml"/><item><title>vSphere 8 Update 3 - What is the "Retain virtual NUMA topology"-feature</title><link>https://www.why-did-it.fail/blog/2024-03-vsphereu3-vnuma-retain/</link><pubDate>Mon, 08 Jul 2024 00:00:00 +0000</pubDate><guid>https://www.why-did-it.fail/blog/2024-03-vsphereu3-vnuma-retain/</guid><description>_ Credits: I would like to thank my colleague Vladimir Petrov from the VCF BU for providing me with additional information that allowed me to write this summary _
The vSphere 8 Update 3 release notes contain lots of changes, but one of them caught my attention:
Cluster-wide option to retain virtual NUMA topology: vSphere 8.0 Update 3 adds a setting to retain preconfigured vNUMA topology even if the VM moves, allowing for better NUMA topology tuning for VMs across all the hosts in the cluster.</description></item></channel></rss>