If you really want to get into it, then could start worrying about your I/O. In the AMD example here: * https://www.thomas-krenn.com/en/wiki/Display_Linux_CPU_

If you really want to get into it, then could start worrying about your I/O. In the AMD example here: * https://www.thomas-krenn.com/en/wiki/Display_Linux_CPU_topology_with_lstopo#Dual_AMD_EPYC_7313 https://www.thomas-krenn.com/en/wiki/Display_Linux_CPU_topol... you'll see some NUMA nodes with networking I/O attached to them, others with NVMe, and others with no I/O. So if you're really worried about network latency then you'd pin the process to that node, but if you want look at disk numbers (a database?) you'd be potentially looking at that node. In recent years there's also chiplet-level locality that may need to be considered as well. Examining this has been a thing in the HPC space for a decade or two now: * https://www.open-mpi.org/projects/hwloc/lstopo/ https://www.open-mpi.org/projects/hwloc/lstopo/ * https://slurm.schedmd.com/mc_support.html https://slurm.schedmd.com/mc_support.html