On Mon, Feb 2, 2015 at 5:18 PM, Hepple, Robert <[email protected]> wrote:
> ... whatever all that means!! And why would it be requesting 704Mb and > 0.2 CPUs? Where do those numbers come from? Adding "Jenkins Slave Memory > in MB" and "Jenkins Executor Memory in MB" comes to 640Mb > The extra overhead is for JVM itself (currently it is set at 10% of requested memory.). In other words when the Jenkins slave is started by Mesos slave it sets "java -Xmx 640MB ....... slave.jar". But the container in which Jenkins slave is spawned has a resource limit of 704MB to account for JVM's own overhead. The math is here: https://github.com/jenkinsci/mesos-plugin/blob/master/src/main/java/org/jenkinsci/plugins/mesos/JenkinsScheduler.java#L273
