On Tue 12-07-22 19:12:18, Abel Wu wrote: [...] > I was just going through the mail list and happen to see this. There > is another usecase for us about per-numa memory usage. > > Say we have several important latency-critical services sitting inside > different NUMA nodes without intersection. The need for memory of these > LC services varies, so the free memory of each node is also different. > Then we launch several background containers without cpuset constrains > to eat the left resources. Now the problem is that there doesn't seem > like a proper memory policy available to balance the usage between the > nodes, which could lead to memory-heavy LC services suffer from high > memory pressure and fails to meet the SLOs. I do agree that cpusets would be rather clumsy if usable at all in a scenario when you are trying to mix NUMA bound workloads with those that do not have any NUMA proferences. Could you be more specific about requirements here though? Let's say you run those latency critical services with "simple" memory policies and mix them with the other workload without any policies in place so they compete over memory. It is not really clear to me how can you achieve any reasonable QoS in such an environment. Your latency critical servises will be more constrained than the non-critical ones yet they are more demanding AFAIU. -- Michal Hocko SUSE Labs
