Linux Server / Performance, Capacity & Containers
Check NUMA topology before changing server CPU or memory placement
A large server's memory locality can affect some workloads even when total CPU and RAM look sufficient. Establish the actual topology.
Environment and inputs: Linux server baseline · Ubuntu 24.04 LTS / RHEL 9-style systems. Use the specified distribution, init system and installed tool; service names, privileges and supported options can differ.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
numactl --hardwareRead the result
With numactl available, this reports visible NUMA nodes, CPUs and memory. VM and container topology may not represent the underlying hardware directly.
Resolve and verify
Compare workload support requirements, process placement and memory pressure before testing a targeted change. Measure the same workload with representative concurrency.
Before changing production
Do not pin production processes or change NUMA policy based only on node counts.