> or allow migration via work stealing (to spread the workload) FWIW, work stealing is often not recommended in thread-per-core architectures because it introd

> or allow migration via work stealing (to spread the workload) FWIW, work stealing is often not recommended in thread-per-core architectures because it introduces quite a bit of unnecessary thread contention. You are correct that load balancing is a central problem in these architectures but it is usually achieved by shedding data since that can be done with minimal locking and inter-thread coordination. This moves the problem to figuring out what data to shed but this has satisfactory inexpensive solutions in many system designs.