# Why NUMA topology became part of managed Slurm placement

AWS PCS exposed NUMA topology and GPU affinity to managed Slurm placement. The change makes locality visible without promising a universal application speedup.

Author: Retrivium editorial team
Language: en
Analysis published: 2026-11-03
Event date: 2026-09-11
Original announcement: https://aws.amazon.com/about-aws/whats-new/2026/09/aws-pcs-gres-hardware-topology-mig/
Canonical URL: https://retrivium.ai/retrospectives/retro-aws-pcs-numa-placement/

AWS PCS made host topology a placement concern on September 11, 2026. A request for a GPU still describes quantity, but CPU affinity and the path between processors and devices describe where the job actually runs. Those are different dimensions of a cluster allocation.

## The managed service came first

The [August 28, 2024 PCS launch](https://aws.amazon.com/about-aws/whats-new/2024/08/aws-parallel-computing-service/) established managed Slurm infrastructure. That reduced the operational work of running a scheduler. It did not make all compute nodes identical, nor did management remove the distinction between local and remote memory access inside a host.

The causal question is therefore about representation: which physical relationships can the scheduler see? Hiding service maintenance is useful; hiding hardware locality from a placement decision can leave an important variable outside the allocation description.

## Hardware variety increased the stakes

[NVIDIA introduced the Blackwell RTX PRO family on March 18, 2025](https://nvidianews.nvidia.com/news/nvidia-blackwell-rtx-pro-workstations-servers-agentic-ai). A hardware family announcement and a managed scheduling feature are separate milestones. The former does not establish that every cloud node has the same CPU layout or interconnect.

For an inference pipeline with substantial CPU preprocessing, the GPU is only one participant. Token preparation, host buffers and transfers can all depend on where CPU work is placed. This is an architectural reason to expose locality, not a measured speedup attributed to the announcement.

## What September exposed

The [PCS update](https://aws.amazon.com/about-aws/whats-new/2026/09/aws-pcs-gres-hardware-topology-mig/) added Slurm 26.05 support, automatic GPU core affinity and GPU interconnect detection. By default, NUMA domains are represented as sockets. Administrators can override the topology, including using L3 cache domains as sockets.

A socket in this scheduler representation should not be casually read as a promise about the number of physical processor packages. The selected representation determines how placement constraints describe the host. Its meaning belongs in the cluster configuration record.

## A useful allocation artifact

Consider a batch that prepares inputs on CPUs and then sends them to an assigned GPU. Its allocation note can contain:

| Field | Question answered |
| --- | --- |
| GPU identity | Which device was assigned? |
| CPU affinity | Which cores are associated with it? |
| NUMA representation | What does a socket mean here? |
| Override version | Which administrator choice changed discovery? |

This note separates hardware discovery from application behavior. A successful launch alone would not establish that preprocessing stayed near the intended device. Conversely, an unexpected runtime does not prove that automatic discovery was wrong.

## The changed decision boundary

The update makes locality available as a scheduling input. It does not prove a universal performance gain, create missing regional GPU inventory or remove the need to understand application data flow. The practical change is a richer explanation of an allocation.

[NUMA and GPU servers](/journal/numa-and-gpu-servers/) explains the locality problem, while [mixed GPU fleets](/journal/mixed-gpu-fleet/) covers heterogeneous resources. Together they show why counting accelerators is necessary but insufficient for describing a placement.