On Tue 23-08-22 14:03:04, Zhaoyang Huang wrote: > On Tue, Aug 23, 2022 at 1:21 PM Michal Hocko <mhocko@xxxxxxxx> wrote: > > > > On Tue 23-08-22 10:31:57, Zhaoyang Huang wrote: [...] > > > I would like to quote the comments from google side for more details > > > which can also be observed from different vendors. > > > "Also be advised that when you enable memcg v2 you will be using > > > per-app memcg configuration which implies noticeable overhead because > > > every app will have its own group. For example pagefault path will > > > regress by about 15%. And obviously there will be some memory overhead > > > as well. That's the reason we don't enable them in Android by > > > default." > > > > This should be reported and investigated. Because per-application memcg > > vs. memcg in general shouldn't make much of a difference from the > > performance side. I can see a potential performance impact for no-memcg > > vs. memcg case but even then 15% is quite a lot. > Less efficiency on memory reclaim caused by multi-LRU should be one of > the reason, which has been proved by comparing per-app memcg on/off. > Besides, theoretically workingset could also broken as LRU is too > short to compose workingset. Do you have any data to back these claims? Is this something that could be handled on the configuration level? E.g. by applying low limit protection to keep the workingset in the memory? > > > > My very vague understanding is that the Android system would like to > > > > freeze specific applications and for that it requires each application > > > > to live in its own cgroup. This clashes with a requirement to age and > > > > reclaim memory on a different granularity (aka no per process reclaim). > > > > So in fact something that cgroup v1 would achieve by having 2 > > > > hierarchies, one for the freezer which would have a dedicated cgroup for > > > > each application and the other for the memory controller where tasks are > > > > grouped by a different criteria. This would rule out that a global (or > > > > any external memory pressure) reclaim would age LRUs that contain a mix > > > > bag of application pages rather than iterate over per-application LRUs. > > > > Is that understanding correct? > > > Correct, this is just our confusion. Besides, we believe that charge > > > the pages to implicit memory enabled parent control group doesn't make > > > sense as the memory cannot be managed at all. > > > > I do not get that part. The parent can manange and control the memory > > usage so how come it cannot be managed at all? > What I mean is the kind of parent which is enabled implicitly by > enabling on its sibling group like belowing hierarchy. Imagine that C > has no intention of memory control but has to be enabled as B would > have it. IMO, it doesn't make sense to charge C1's memory.current to C > until an explicitly echo "+memory" > C/subtree_control. > A----B---B1 > \ C---C1 So let me just expand your example for clarity A.cgroup.controllers = memory A.cgroup.subtree_control = memory A/B.cgroup.controllers = memory A/B.cgroup.subtree_control = memory A/B/B1.cgroup.controllers = memory A/C.cgroup.controllers = memory A/C.cgroup.subtree_control = "" A/C/C1.cgroup.controllers = "" Is your concern that C1 is charged to A/C or that you cannot actually make A/C.cgroup.controllers = "" because you want to maintain memory in A? Because that would be breaking the internal node constrain rule AFAICS. Or maybe you just really want a different hierarchy where A == root_cgroup and want the memory acocunted in B (root/B.cgroup.controllers = memory) but not in C (root/C.cgroup.controllers = "")? That would mean that C memory would be maintained on the global (root memcg) LRUs which is the only internal node which is allowed to have resources because it is special. -- Michal Hocko SUSE Labs
