<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>JVM on Dhaval Shah</title><link>https://www.dhaval-shah.com/categories/jvm/</link><description>Recent content in JVM on Dhaval Shah</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Mon, 04 Apr 2022 07:00:50 +0000</lastBuildDate><atom:link href="https://www.dhaval-shah.com/categories/jvm/index.xml" rel="self" type="application/rss+xml"/><item><title>G1 GC - A primer from performance engineering standpoint</title><link>https://www.dhaval-shah.com/g1-gc-primer/</link><pubDate>Mon, 04 Apr 2022 07:00:50 +0000</pubDate><guid>https://www.dhaval-shah.com/g1-gc-primer/</guid><description>Background In couple of my previous articles I not only tried helping understand fundamentals of JVM memory management, but also delved deeper to understand how Garbage Collection works along with its optimization. So with this background, I am sure you would be convinced that behavior of garbage collection may have ramification on performance of an application.
With newer versions of Java, garbage collection has also evolved from Serial -&amp;gt; Parallel -&amp;gt; CMS -&amp;gt; G1 GC -&amp;gt; Z GC.</description></item><item><title>Understanding nuances of garbage collection and ways to tune it with real world example</title><link>https://www.dhaval-shah.com/understanding-and-optimizing-garbage-collection/</link><pubDate>Sun, 17 Nov 2019 18:37:16 +0000</pubDate><guid>https://www.dhaval-shah.com/understanding-and-optimizing-garbage-collection/</guid><description>In one of my previous post I elaborated basics of JVM memory and also explained how garbage collection works. In this post we will try to understand various types of GC and how to tune and optimize them with a real world example.
GC Taxonomy 1. Minor GC When garbage is collected from Young space it is called Minor GC.
Characteristics Triggered when JVM is unable to allocate space for a new object in Eden space.</description></item><item><title>Understanding JVM Memory Management</title><link>https://www.dhaval-shah.com/understanding-jvm-memory-management/</link><pubDate>Mon, 23 Oct 2017 04:44:34 +0000</pubDate><guid>https://www.dhaval-shah.com/understanding-jvm-memory-management/</guid><description>Everyone of us as Software Engineers would have experienced memory leaks, OOM errors in our Java/JVM applications? In order to dissect such issues it is extremely important to understand the whats' and hows' of JVM memory and its management.
JVM - Memory Management One of the many strengths of the JVM is that it performs automatic memory management. As we all know memory management is the process of allocating objects, determining when those objects are no longer needed; thereby de-allocating the memory used by those objects and making it available for future allocations</description></item></channel></rss>