Many articles describe how a poorly tuned garbage collector can bring an application's SLA commitments to its knees.
Oracle's new G1 Collector in HotSpot moves away from the conventional GC model, where a Java heap splits into (contiguous) young and old generations, and instead introduces the concept of “regions”, for a generally more performant and manageable GC.
Analyzing and tuning the Garbage collection in JVM can be difficult thing to do. Most java applicati...
This is list of some Java fundamental questions and answers, which are commonly asked in a Core Java...
Performance engineer Monica Beckwith covers tuning java garbage collection, including: defining customer requirements; methodology; baselining and measurement; strengths and weaknesses of the different collectors; heap usage; causes of GC pauses; the distribution of pauses; tuning pause characteristics; going off-heap to avoid collection; scaling GC on multi-core and high memory machines.
To diagnose any memory problems, the Garbage Collection log file is the best place to start. Take a look at the anatomy of a GC log file in this helpful article.
Java Memory Architecture (Java Memory Model)The above is the Java Memory Model for the Heap ...
list of useful tuts
