Description When there is a performance bottleneck in the application, most of the threads will start to accumulate on that problematic bottleneck area. Those threads will have same stack trace. Thus whenever a significant number of threads exhibit identical/repetitive stack trace then those... Continue Reading →
Description If several threads in a thread dump end up working on one single method, then it might be of concern. Most of the times, if there is a problem (say poorly responding data source, un-relinquished lock, infinite looping threads... Continue Reading →
Description Objects that have finalize() method are treated differently during Garbage collection process than the ones which don't have them. During garbage collection phase, object with finalize() aren't immediately evicted from the memory. Instead as first step, those objects are added... Continue Reading →
This is an old, outdated article. We have devised a better and simpler strategy to troubleshoot CPU spikes in this article. Have you ever encountered circumstance where your applications CPU maxes out and never goes down even if traffoc volume goes down?... Continue Reading →
Description Based on the type of GC algorithm (Serial, parallel, G1, CMS) used, default number of garbage collection threads gets created. Details on default number of threads that will be created are documented below. Sometimes too many extraneous GC threads would get created based... Continue Reading →
In this training program, engineers will be equipped with necessary knowledge to optimize CPU, memory and response time.