You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2019/03/13 20:17:00 UTC
[jira] [Commented] (MESOS-9634) Soft CPU limit for windows
JobObject
[ https://issues.apache.org/jira/browse/MESOS-9634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16792077#comment-16792077 ]
Benjamin Mahler commented on MESOS-9634:
----------------------------------------
Linked in a related ticket, I thought we had a ticket for "burstable containers" but I can't seem to find one.
> Soft CPU limit for windows JobObject
> ------------------------------------
>
> Key: MESOS-9634
> URL: https://issues.apache.org/jira/browse/MESOS-9634
> Project: Mesos
> Issue Type: Wish
> Components: allocation, containerization
> Reporter: Andrei Stryia
> Priority: Major
>
> We are using Mesos to run Windows payload. As I see, CPU utilization on the slave nodes is not very good. Because of the hard cap limit, process cannot use more CPU resources even if there are a lot of free CPU resources at the moment (e.g. only one task is started on the node at the moment).
> I know, the reason of such behavior is {{JOB_OBJECT_CPU_RATE_CONTROL_HARD_CAP}} control flag of the Job Object.
> But what about ability to use {{JOB_OBJECT_CPU_RATE_CONTROL_MIN_MAX_RATE}} control flag, where MinRate will be limit specified in Task config while MaxRate will be 100%CPU. This option will work the same way as cgroups/cpu and add more elasticity.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)