<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gc on Random Ramblings</title><link>https://blog.foundev.pro/tags/gc.html</link><description>Recent content in Gc on Random Ramblings</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 03 Feb 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.foundev.pro/tags/gc/index.xml" rel="self" type="application/rss+xml"/><item><title>Heap Size Around 32 GB</title><link>https://blog.foundev.pro/2021/02/03/heap-size-around-31gb.html</link><pubDate>Wed, 03 Feb 2021 00:00:00 +0000</pubDate><guid>https://blog.foundev.pro/2021/02/03/heap-size-around-31gb.html</guid><description>&lt;h1&gt;Heap Size Around 32 GB&lt;/h1&gt;&#10;note: originally written Feb 3 2021&#10;&lt;p&gt;There was a question this morning around a pretty common discussion point around 31 gb versus 32 gb of heap. This &lt;a href="http://java-performance.info/over-32g-heap-java/"&gt;article discusses this in more detail&lt;/a&gt;, the key point follows:&lt;/p&gt;&#10;&lt;blockquote&gt;&#10;&lt;p&gt;Be careful when you increase your application heap size over 32G (from under 32G to over 32G) – JVM switches to 64 bit object references at that moment, which means that your application may end up with less available heap space. A rule of thumb is to jump from 32G right to 37-38G and continue adding memory from that point. The actual area of “grey” territory depends on your application – the bigger an average Java object in your application, the smaller is the overhead.&lt;/p&gt;</description></item></channel></rss>