The Chicago Coder Conference featured 15 tracks and over 100 sessions across two days. Architect Ram Lakshmanan presented on Java Garbage Collection Logs, garnering positive feedback and engaging discussions. The presentation titled “How to Become a Garbage Collection (GC) Hero” received excellent reviews, as reflected in the speaker survey results.
String deduplication saves memory by replacing repeated strings with references to just one copy. In Java, this can be done using the intern() method. In Java 8, specific settings are needed to activate this feature, while newer versions handle it automatically. Reviewing string deduplication logs helps assess how well memory is being used.
In this article, we are going to compare the performance of Garbage Collection(GC) of OpenJDK and GraalVM. The GraalVM is a popular open source JVM implementation in Java with a capability to run applications as native images. Apart from that, it has got other functionalities such as fast loading time, compacted memory usages,etc. Let’s compare the... Continue Reading →
Developers once managed memory manually, leading to leaks. Java's 1995 introduction of automatic garbage collection shifted this responsibility to the JVM. GC throughput, measuring time spent on processing versus garbage collection, is crucial for performance. Optimizing this throughput requires addressing issues like memory leaks, tuning, and resource allocation for better application efficiency.
Coming soon
coming soon
The post discusses various garbage collection (GC) patterns observable in applications, including healthy saw-tooth patterns, heavy caching, acute memory leaks, consecutive full GC, and metaspace memory problems. By analyzing these patterns, developers can assess application performance and identify potential memory issues, ultimately improving application health and efficiency.
This article discusses how to simulate and diagnose StackOverflow errors in Java. It introduces a sample program that triggers a StackOverflowError due to infinite recursion in the start() method of the StackOverflowDemo class. Both manual and automated approaches for diagnosing the error are outlined, highlighting the effectiveness of the yCrash tool for root cause analysis.
