You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jie Yu (JIRA)" <ji...@apache.org> on 2018/08/20 04:37:00 UTC
[jira] [Assigned] (MESOS-9081) cgroups::verify is expensive and is
done implicitly during cgroups operations
[ https://issues.apache.org/jira/browse/MESOS-9081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jie Yu reassigned MESOS-9081:
-----------------------------
Assignee: Jie Yu
> cgroups::verify is expensive and is done implicitly during cgroups operations
> -----------------------------------------------------------------------------
>
> Key: MESOS-9081
> URL: https://issues.apache.org/jira/browse/MESOS-9081
> Project: Mesos
> Issue Type: Improvement
> Components: containerization
> Reporter: Benjamin Mahler
> Assignee: Jie Yu
> Priority: Major
> Labels: performance
>
> See MESOS-8418 for how this initially came up.
> Currently, many of the cgroup helper functions perform an internal verify:
> https://github.com/apache/mesos/blob/1.6.0/src/linux/cgroups.cpp#L922
> This reads /procs/mounts to see which cgroups subsystems are mounted, and /proc/mounts can get rather large and expensive to read.
> The steady state case (polling /containers and /monitor/snapshot to retrieve container resource usage statistics) was addressed with a short term patch in MESOS-8418. However, we should consider some longer-term fixes that address performance of other events that incur cgroup operations (e.g. updating resources of a container, launching a container, etc):
> 1. Consider moving the verify function to public and have the isolators use it where appropriate.
> 2. Complementary to 1, optimize verify (e.g. read /proc/self/mountstats as suggested in MESOS-8418).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)