Hacker GitHub

← All repos

cloudfoundry/java-buildpack-memory-calculator

View on GitHub ↗ ★ 671 Go

Cloud Foundry JVM Memory Calculator

5 mentions on Hacker News by 3 people: 0 stories, 5 comments · first 2017-10-22 · latest 2019-12-22

Mentions per year 5 mentions · busiest year 2018 (3)
20082026
  1. The JVM hasn't yet become fully container-friendly because it bases its calculation on the host OS figures, not the container figures. You can use a calculator to get precise, proven settings for any supported JVM:…
    comment by jacques_chester · 2019-12-22 · in Go + Services = One Goliath Project
  2. Yes, we do. It's actually a rather small setup (13 dedicated server, about 100 containers). The absolutely most basic advice is probably: "-Xmx" does not represent the actual upper limit for memory usage. We actually most often only set…
    comment by mboehm · 2018-03-21 · in Running Java in a Container
  3. We run in production with conservative memory limits. If you want to be more clever, you could try this: https://github.com/cloudfoundry/java-buildpack-memory-calcul...
    comment by oftenwrong · 2018-03-21 · in Running Java in a Container
  4. In particular, the Java buildpack uses a component developed entirely to calculate JVM settings. I am not sure what the plans are for Java 9 and 10 yet. Ben Hale works on JBP pretty much fulltime and the Spring team tend to experiment…
    comment by jacques_chester · 2018-03-21 · in Running Java in a Container
  5. > Most of the time it did not matter that much to give the Server a GB more memory but recently we had some real issues with CloudFoundry. A long-standing difficulty with the Java Buildpack was working out how much memory to give it -- the…
    comment by jacques_chester · 2017-10-22 · in Debunking the Java Performance Myth