Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>There is no single answer to this question, it is highly depending on what your application is doing and how it manages its objects. Maybe have a look at <a href="http://chaoticjava.com/posts/how-does-garbage-collection-work/" rel="noreferrer">How does garbage collection work</a> and <a href="http://chaoticjava.com/posts/parallel-and-concurrent-garbage-collectors/" rel="noreferrer">Parallel and concurrent garbage collectors</a> to understand the various options. </p> <p>Then, check the <a href="http://java.sun.com/javase/technologies/hotspot/gc/gc_tuning_6.html" rel="noreferrer">Java SE 6 HotSpot[tm] Virtual Machine Garbage Collection Tuning</a> document that expands on GC tuning concepts and techniques for Java SE 6 that were introduced in the <a href="http://java.sun.com/docs/hotspot/gc5.0/gc_tuning_5.html" rel="noreferrer">Tuning Garbage Collection with the 5.0 Java Virtual Machine</a> document.</p> <p>If you want to keep garbage collection pauses short, the concurrent collector is likely the right direction as it performs most of its work concurrently (i.e., while the application is still running). But finding the best setup will require profiling (consider measuring the GC throughput, the max and average pause time, the frequency of full GCs and their duration too).</p> <p>(EDIT: Having read a comment from the OP, I think that reading <a href="http://kirk.blog-city.com/advice_on_jvm_heap_tuning_dont_touch_that_dial.htm" rel="noreferrer">My advice on JVM heap tuning, keep your fingers off the knobs!</a> from the performance guru Kirk Pepperdine would be a good idea.)</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload