Search

GC easy – Universal Java GC Log Analyser

Tag

garbage collection

Automobile company optimizes performance using GCeasy

One the world’s largest automobile manufacturers has optimized their middleware platform’s response time by several folds. This world renowned enterprise optimized their garbage collection performance using our GCeasy tool and was able to reduce their overall application’s response time by a stunning 49.46%

Continue reading “Automobile company optimizes performance using GCeasy”

Garbage Collection CPU Statistics

When a Garbage Collection event runs, it spends a predominant amount of its time in the Java application layer. It also spends a certain portion of its time in the Operating System/Kernel layer. 

Continue reading “Garbage Collection CPU Statistics”

In which region intern strings are stored?

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?”

Java Hashtable, HashMap, ConcurrentHashMap – Performance impact

There are a good number of articles that articulate functional differences between HashMap, HashTable and ConcurrentHashMap. This post compares the performance behavior of these data structures through practical examples. If you don’t have patience to read the entire post, here is bottom line: When you confront with the decision of whether to use HashMap or HashTable or ConcurrentHashMap, you can consider using ConcurrentHashMap since it’s thread-safe implementation, without compromise in performance.

Continue reading “Java Hashtable, HashMap, ConcurrentHashMap – Performance impact”

Let’s crash the applications! – Confoo 2022

ConFoo Montreal is a multi-technology conference for developers. This year , they have conducted the program to exchange knowledge and ideas from speakers all over the world. Our Architect Ram Lakshmanan was invited to give a talk on the topic: “Let’s crash the applications!”

Continue reading “Let’s crash the applications! – Confoo 2022”

Garbage Collection tuning success story – reducing young gen size

When you tune Garbage collection performance, you are not only improving Garbage collection pause time but also the overall application’s response time and reducing cloud computing cost. Recently we helped to tune the Garbage collection behavior of a popular application. Just by making a minor change, it resulted in a dramatic improvement. Let’s discuss this garbage collection tuning success story in this post.

Continue reading “Garbage Collection tuning success story – reducing young gen size”

16 artifacts to capture when there is a production problem -Montreal 2022

ConFoo Montreal is a multi-technology conference for developers. Our Architect Ram Lakshmanan has been invited there to present on the topic “16 artifacts to capture when there is a production problem“, which has secured 5th place among 155 sessions.

Continue reading “16 artifacts to capture when there is a production problem -Montreal 2022”

7 habits of highly effective Performance Troubleshooters! – All Day Devops Conference

The World’s Largest 6th Annual All Day DevOps conference held on October 28th 2021. Our architect Ram Lakshmanan was invited there to present a webinar on the topic 7 habits of highly effective Performance Troubleshooters!

Below is the deck shared in the conference which explains, how to forecast the problems?, what to do when the problem is happening?, how to identify the root cause instantly? and how to prevent problems from happening in the future and so on.

Continue reading “7 habits of highly effective Performance Troubleshooters! – All Day Devops Conference”

Detect proactively whether application’s memory is under-allocated

 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”

Powered by WordPress.com.

Up ↑