Automatic garbage collection is a prevalent feature in modern programming languages such as Golang, Node.js, Java, .NET, and Python. While it offers convenience to developers by automatically removing unreferenced objects from memory, it can also result in excessive CPU consumption. As applications continuously create numerous objects, the garbage collector runs continuously in the background to reclaim these objects, consuming a significant number of CPU cycles. However, measuring the exact CPU cycles consumed due to automatic garbage collection can be challenging for many developers. In this article, we will explore a few approaches to measure the CPU cycles consumed by automatic garbage collection.
Continue reading “Is Garbage Collection Consuming High CPU in My Application?”
Time taken by every single GC event is reported in the GC log. In every GC event, there are ‘user’, ‘sys’, and ‘real’ time. Continue reading “SYS TIME GREATER THAN USER TIME”
Time taken by every single GC event is reported in the GC log. In every GC event, there are ‘user’, ‘sys’, and ‘real’ time. Continue reading “REAL TIME IS GREATER THAN USER AND SYS TIME”
Long GC Pauses are undesirable for applications. It affects your SLAs; it results in poor customer experiences, and it causes severe damages to Continue reading “REDUCE LONG GC PAUSES”