I have noticed that without explicit flags, the mesos-agent does not
restrict a cgroup of a container to any CPUSET. This has quite
deleterious consequences in our usage model where the OS threads in
containerized processes migrate to any NUMA sockets over time and lose
locality to memory they allocated with the first touch policy. It would
take a lot of effort to specify the exact CPUSET at the container launch

I am wondering if the mesos agent can expose a flag (e.g.,
--best-effort-numa-locality) so that if the requested number of CPU share
and memory demands meet the requirements, then the container can be
launched with the cgroup affinity set to a single NUMA socket and avoid any
deleterious effects of unrestricted CPU migration.


Reply via email to