| |||||||||||||
Interview with Lennart Poettering (LinuxFR.org)Interview with Lennart Poettering (LinuxFR.org)Posted Jul 6, 2011 18:34 UTC (Wed) by SEJeff (subscriber, #51588)In reply to: Interview with Lennart Poettering (LinuxFR.org) by dlang Parent article: Interview with Lennart Poettering (LinuxFR.org)
Just out of curiosity, can you link to any benchmarks or whatnot on the overhead of cgroups? I'm not saying they don't impact things, but am curious if this has actually be quantified using some synthetic benchmarks or whatnot.
(Log in to post comments)
Interview with Lennart Poettering (LinuxFR.org) Posted Jul 6, 2011 19:02 UTC (Wed) by dlang (✭ supporter ✭, #313) [Link]
I think there have been a number of discussions recently (on the kernel list and on LWN that have talked about the overhead of cgroups (in part because they are bolted on rather than fully integrated.
I could be remembering things incorrectly.
but in any case, as a standard security best practice, if I don't need a feature I don't enable it. This also makes my systems more reliable as there is less code compiled in.
Interview with Lennart Poettering (LinuxFR.org) Posted Jul 6, 2011 22:38 UTC (Wed) by mezcalero (subscriber, #45103) [Link]
systemd requires only the grouping part of cgroup, i.e. no controllers. The impact of some controllers might be high, but the basic grouping logic is barely measurable.
The people who complain the loudest tend to mix up cgroups with its controllers. I'd prefer if people could make the distinction there. But hey, if people were well informed they probably wouldn't whine that loud. Educated whining?
|
|||||||||||||