The JVM has internal memory regions, and Native Memory Tracking (NMT) helps find memory problems in these areas. NMT gives details on memory allocation and usage, making it useful for spotting memory leaks. To enable NMT, use the -XX option, and analyze the data for better application performance. The post Understanding Native Memory Tracking (NMT) in Java appeared first on GC easy - Universal Java GC Log Analyser ..read more

Java application creates several objects to service the new incoming requests. For instance, when a customer signs on, our applications creates following objects: an HTTP request object, HTTP session object, HTTP filter object, Servlet object, customer object (which internally includes username and password string objects), a DAO object for backend database interaction, a connection object for database connection, and a ResultSet object, once the database responds and several such objects.  Once the request is serviced, these newly created objects will become useless. Because these object ..read more

As an engineer, we deal with only 4 primary computing resources: CPU Memory Network Storage Among these resources, most enterprise Java applications tend to saturate memory first, before hitting the limits of the other three resources. When memory becomes a bottleneck, you end up provisioning additional computing capacity even though the other 3 resources (CPU, network, and storage) are partially or under-utilized.  However, in several applications more memory is allocated than the actual need. This over-allocation leads to an unnecessary increase in computing costs. When memory is over ..read more

Automatic Garbage Collection is one of the core features of Java programming language, which facilitates developers to focus on writing business logic code and not worry about de-allocating the objects, which developers had to do in the predecessor language (C, C++). However, this automatic Garbage Collection pauses your application to remove unreferenced objects from memory.  During this pause period, no customer transactions will be processed. These pauses can range anywhere from a few milliseconds to several seconds (sometimes even minutes). When you reduce this Garbage Collection paus ..read more

A major insurance company improved its overall application throughput by tuning their Garbage Collection (GC) behavior. In this post, let’s study the bottleneck they faced, the GC tuning methodology they employed, and the settings that enhanced their application throughput. Identifying the GC Performance Bottleneck The Insurance application would handle the incoming transactions properly, however starting from 10am till 4pm it will be intermittently unresponsive to the requests. The SRE team suspected this unresponsiveness was happening due to Garbage Collection pauses. Thus, they captured the ..read more

GC log contains a rich source of metrics that is often studied to reduce GC pause time, forecast memory problems, improve application response time, reduce computing cost and do effective capacity planning. In this post, we would like to share best practices on GC Logging that you may find useful. 1. Enable GC Log with Right Arguments JVM generates GC logs automatically in the specified file path when you pass certain arguments. You have to be watchful of what argument you pass. Because inappropriate arguments can either generate an overwhelming amount of unnecessary data or prevent critical d ..read more

There’s a famous saying: “If you can’t measure it, you can’t improve it.” This is especially true for Garbage Collection (GC) tuning. However, there are numerous GC metrics to consider, each providing insights into different aspects of your application’s performance and behavior. But not all metrics are equally important. In this post, we’ll focus on the key GC metrics that have the most significant impact on your application’s efficiency and stability. By understanding and monitoring these critical metrics, you can make informed decisions when optimizing GC Performance. Key Garbage Collection ..read more

As a Java engineer, you might wonder which GC algorithm to use for your application. Choosing the GC algorithm is like choosing a life partner for your application. Seriously , there are a lot of similarities: The GC coexists with your application under the same roof (i.e., the JVM). GC keeps cleaning up the mess (i.e., garbage) created by your application. If the application gets aggressive and creates a lot of objects, GC will also become aggressive and reclaim them from memory. Both GC and your application continuously fight for the same CPU cycles. Just like how choosing the right life p ..read more

Coming soon… The post 9 Tips to Reduce Long Garbage Collection Pauses appeared first on GC easy - Universal Java GC Log Analyser ..read more

Coming Soon… The post Java GC Tuning: Improved Throughput of an Insurance Company appeared first on GC easy - Universal Java GC Log Analyser ..read more