[JIRA] (JENKINS-49317) Combination of '-daemon' and '-XX:+AlwaysPreTouch' will not let you use more than ~40% of all available memory

[jayanmn@gmail.com (JIRA)]

Jayan MN commented on JENKINS-49317

Re: Combination of '-daemon' and '-XX:+AlwaysPreTouch' will not let you use more than ~40% of all available memory This affects what is written in blog : https://jenkins.io/blog/2016/11/21/gc-tuning/ : Tuning Jenkins GC For Responsiveness and Stability with Large Instances  options "-server" and  -XX:+AlwaysPreTouch caused above error. Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[jayanmn@gmail.com (JIRA)]

Jayan MN edited a comment on JENKINS-49317

Re: Combination of '-daemon' and '-XX:+AlwaysPreTouch' will not let you use more than ~40% of all available memory

This affects what is written in blog : [ https://jenkins.io/blog/2016/11/21/gc-tuning/ ]  : Tuning Jenkins GC For Responsiveness and Stability with Large Instances  options "-server" and  -XX:+AlwaysPreTouch caused above error.

Now large memory instances are very common. A fix  here will help Jenkins user experience and adoption

Add Comment

[owen@nerdnetworks.org (JIRA)]

Owen Mehegan commented on JENKINS-49317

Re: Combination of '-daemon' and '-XX:+AlwaysPreTouch' will not let you use more than ~40% of all available memory

This problem can be avoided by setting -Xms to a value less than half of physical RAM. I realize that there is some performance penalty to each allocation of more RAM above the min heap size value, but once allocated the JVM will not deallocate that heap, so this might only occur a couple of times in the Jenkins service life cycle.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)