Search

GC easy – Universal Java GC Log Analyser

Tag

Java GC

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”

Overhead added by Garbage Collection Logging

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”

What is Java Heap Fragmentation?

Java Heap fragmentation is an interesting problem, which triggers long pausing full garbage collection cycles. In this article we would like to attempt to explain the heap fragmentation. 

Let’s say developer write a code ‘new BMW()’. This will create a new BMW object in the heap memory space. Example:

Continue reading “What is Java Heap Fragmentation?”

7 JVM arguments of Highly Effective Applications

At the time (March 2020) of writing this article there are 600+ arguments that you can pass to JVM just around Garbage collection and memory. If you include other aspects, total JVM arguments count will easily cross 1000+. 😊. It’s way too many arguments for anyone to digest and comprehend. In this article, we are highlighting seven important JVM arguments that you may find it useful.

Continue reading “7 JVM arguments of Highly Effective Applications”

GCeasy API – Remote Location

In Garbage collection log analysis API we have introduced a new feature called Remote Location. Using this feature now you can pass the http(s) URL location of your GC log in the request.

Continue reading “GCeasy API – Remote Location”

GCEASY API – TIME FILTERS

Sometimes users want to analyze GC logs for a certain time interval instead of analyzing the entire GC Log. Here are the use cases for it:

Continue reading “GCEASY API – TIME FILTERS”

HOW GCEASY AND FAST THREAD ARE COMPARED TO JVISUALVM?

A potential customer asked us this question: “How GCEasy & FastThread are compared to JVisualVM?”. As it was a great question, here was our answer:

QUESTIONING STATUS QUO – ‘SERIAL GC NOT FOR SERIOUS APPLICATIONS’

In several journals, articles, blogs and all throughout the internet there is one common theme echoed: “Serial GC is not meant for any serious applications. It should be used only for prototype application. It’s only meant for desktop application or applications that have few hundred MBs of heap size. It shouldn’t be used in production.” To question this status quo theme, we conducted the below study on a major travel web services application in North America (Kindly apologizes, I can’t disclose their name).

Continue reading “QUESTIONING STATUS QUO – ‘SERIAL GC NOT FOR SERIOUS APPLICATIONS’”

A CASE STUDY: DIFFERENT GC ALGORITHMS BEHAVIOR IN PRODUCTION

On a major B2B application different GC algorithms behaviors were studied. This application is basically a web service provider servicing SOAP and REST requests from its clients.

Continue reading “A CASE STUDY: DIFFERENT GC ALGORITHMS BEHAVIOR IN PRODUCTION”

Powered by WordPress.com.

Up ↑