4 ms·
> Go, however, used a lot less memory, which means that it can scale down to smaller instances. I could be mistaken, but this sounds like they went ahead with
by apta 7y ago
> Go, however, used a lot less memory, which means that it can scale down to smaller instances.
I could be mistaken, but this sounds like they went ahead with the default JVM settings, where it tends to use as much memory it is allowed to (which makes sense from a utilization and efficiency perspective). If memory usage is a concern, the JVM can be tuned for such.
- jacques_chester 7y agoThe 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: https://github.com/cloudfoundry/java-buildpack-memory-calculator/ https://github.com/cloudfoundry/java-buildpack-memory-calcul...
- apta 7y agoI thought this was a solved issue since JDK 10: https://www.docker.com/blog/improved-docker-container-integration-with-java-10/ https://www.docker.com/blog/improved-docker-container-integr...
- jacques_chester 7y agoIn my understanding, no. It's improved but not fully "fixed". Unfortunately that's as far as my understanding extends.