Comment # 6 on bug 954765 from Mel Gorman

(In reply to Franck Bui from comment #5)
> (In reply to Mel Gorman from comment #4)
> > It is possible this was an oversight. I do not have the full picture of what
> > was planned but it appears that the intent was to activate this only for new
> > containers. It's just the case that in Tumbleweed that normal sessions (or
> > at least ssh sessions from root) are also impacted. If only processes within
> > a container or a VM were resource controlled then it would limit the impact
> > of this bug.
> 
> I think the intent was to really activate this for 'root' user sessions too.
> Regular user sessions are left alone for now unless unified hierarchy is
> supported and used by the kernel.
> 

This means that any process launched by root be it manual launch of a server or
a benchmark is going to be throttled. It cannot be what they really intended or
if they did, it's a massive overhead to occur for very little, if any, gain.

> See commit which introduced the Delegate property for some details:
> https://github.com/systemd/systemd/commit/
> a931ad47a8623163a29d898224d8a8c1177ffdaf

The commit to me seems to say that it was only intended to be activated for
containers :(