intern() is an interesting function in java.lang.String object. intern() function eliminates duplicate string objects from the application and has potential to reduce overall memory consumption of your application. To understand how string intern() function works you may refer to this interesting blog. Intern strings are stored in a string pool in the JVM memory. JVM Memory has following regions:
Continue reading “In which region intern strings are stored?”
Analyzing garbage collection log provides several advantages like: Reduces GC pause time, reduces cloud computing cost, predicts outages, provides effective metrics for capacity planning. To learn about the profound advantages of GC log analysis, please refer to this post. In this post let’s learn how to analyze GC logs?
Continue reading “How to do GC Log analysis?”
When the application’s memory is under-allocated, it will result in the following side-effects:
a. Transactions response time will degrade
b. CPU consumption will spike up
c. OutOfMemoryError will be thrown
Only when OutOfMemoryError is thrown, most of us start to look at our application’s memory settings. This is like only when a patient goes to a critical condition; we begin to give treatment :-).
In this post, let’s discuss how to detect whether your application’s memory is under-allocated or not in a proactive manner.
Continue reading “Detect proactively whether application’s memory is under-allocated”
Enabling Garbage collection logs on your application has certain advantages. In nutshell, Garbage collection logs will facilitate you to optimize Garbage Collection pause time, improve overall application’s response time, forecast production outages, reduce computing cost. Even though Garbage collection logs have these advantages, we weren’t sure what overhead does garbage collection logging add to the application. Thus we set out to conduct the below case study.
Continue reading “Overhead added by Garbage Collection Logging”
I have heard a few of my developer friends say: “Garbage Collection is automatic. So, I do not have to worry about it.“ The first part is true, i.e., “Garbage Collection is automatic” on all modern platforms – Java, .NET, Golang, Python… But the second part i.e., “I don’t have to worry about it.” – may not be true. It is arguable, questionable. Here is my case to showcase the importance of Garbage Collection:
Continue reading ““I don’t have to worry about Garbage collection” – Is it true?”
Eclipse and IntelliJ are the two competing IDEs in the industry. There are lot of passionate discussion going in the social media, forums to declare the winner in this race. We thought it would be a fun exercise to study which IDE utilizes memory efficiently?
Continue reading “MEMORY EFFICIENT: ECLIPSE OR INTELLIJ?”
There are 3 highly popular myths about Garbage Collection. Let’s review those myths and the actual truth behind them.
Continue reading “3 POPULAR MYTHS ABOUT GARBAGE COLLECTION”
I have heard from few of my developer friends saying: “Garbage Collection is Automatic. So, I don’t have to worry about it.” Continue reading “WHY GARBAGE COLLECTION MIGHT BE MORE IMPORTANT THAN YOU THINK?”
Enabling GC logging provides great benefits such as: reducing overall application response time, troubleshooting memory problems, forecast outages, and doing effective capacity planning… Contrary to common thinking, enabling GC logging doesn’t add any noticeable overhead to your application. Thus, we strongly recommend you enable GC logging on all your production servers.
Continue reading “WHAT IS GARBAGE COLLECTION LOG? HOW TO ENABLE & ANALYZE?”