NHacker Next
  • new
  • past
  • show
  • ask
  • show
  • jobs
  • submit
NUMA: Cores, memory, and the distance between them (edera.dev)
lukax 2 hours ago [-]
NUMA can cause really crappy performance. We deployed a Go based LLM gateway in Kubernetes deployed on a server with hundreds of CPU cores. We didn't explicitly set GOMAXPROCS so Go runtime scheduled goroutines over different CPUs and it constantly used 200% CPU and GC was causing latency spikes. Then we set GOMAXPROCS 8 and all performance issues went away. Until recently Kubernetes didn't work well with NUMA.
CarRamrod 20 minutes ago [-]
There is one instance where the NUMA performance never disappoints: https://www.youtube.com/watch?v=Cqd1Gvq-RBY
re-thc 2 hours ago [-]
Is this on AMD? I wonder if it's all to do with NUMA or their CCD architecture etc (well these days Intel and everyone also does it to some extent).
toast0 1 hours ago [-]
Hundreds of cores is likely two sockets and so you've got NUMA there.

Scaling to large core counts has a lot of gotchas.

1 hours ago [-]
StreamCtx 1 hours ago [-]
[dead]
Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact
Rendered at 12:01:49 GMT+0000 (Coordinated Universal Time) with Vercel.