[
https://issues.apache.org/jira/browse/MESOS-7006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15853789#comment-15853789
]
haosdent commented on MESOS-7006:
---------------------------------
Refer to https://docs.docker.com/engine/reference/run/#/cpu-period-constraint
{code}
For example, if there is 1 CPU, then --cpus=0.5 will achieve the same result as
setting --cpu-period=50000 and --cpu-quota=25000 (50% CPU).
{code}
This issue looks duplicated with what [~zhitao] do before.
https://issues.apache.org/jira/browse/MESOS-6134 Should we mark this
duplicated?
[~jieyu][~gilbert][~janisz]
Another option is we put off this after we have a better way to validate
docker's version and handle compatible logics.
> Launch docker containers with --cpus instead of cpu-shares
> ----------------------------------------------------------
>
> Key: MESOS-7006
> URL: https://issues.apache.org/jira/browse/MESOS-7006
> Project: Mesos
> Issue Type: Improvement
> Affects Versions: 1.1.0
> Reporter: Craig W
> Assignee: Tomasz Janiszewski
>
> docker 1.13 was recently released and it now has a new --cpus flag which
> allows a user to specify how many cpus a container should have. This is much
> simpler for users to reason about.
> mesos should switch to starting a container with --cpus instead of
> --cpu-shares, or at least make it configurable.
> https://blog.docker.com/2017/01/cpu-management-docker-1-13/
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
