[
https://issues.apache.org/jira/browse/MESOS-6690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16245476#comment-16245476
]
Alexander Rukletsov commented on MESOS-6690:
--------------------------------------------
{noformat}
Commit: 8ffc3541482be3d615de7054ddb50b3905fd8952 [8ffc354]
Author: Andrew Schwartzmeyer <and...@schwartzmeyer.com>
Date: 9 November 2017 at 11:26:54 GMT+1
Committer: Alexander Rukletsov <al...@apache.org>
Increased check tests task resources for Windows.
Unfortunately, due to PowerShell's resource usage as a .NET program, on
Windows 32 MB is not enough memory to run these tests. One instance of
PowerShell takes > 128 MB, and two instances take > 256 MB.
Realistically, the safe minimum is 512 MB of memory.
Review: https://reviews.apache.org/r/63279/
{noformat}
> Wire up resource control API to Windows Job objects API
> -------------------------------------------------------
>
> Key: MESOS-6690
> URL: https://issues.apache.org/jira/browse/MESOS-6690
> Project: Mesos
> Issue Type: Bug
> Components: agent, containerization
> Reporter: Alex Clemmer
> Assignee: Andrew Schwartzmeyer
> Labels: microsoft, windows-mvp
>
> The Windows version of the containerizer actually launches tasks in the Job
> object API, which means that it should be possible to wire up the Mesos
> resource constraint API and use those constraints when we launch a task.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
