Which Garbage Collector should be used in AEM 6.2 | Community
Skip to main content
sandeepk1310028
sandeepk1310028
Level 2
June 12, 2017
Solved

Which Garbage Collector should be used in AEM 6.2

  • June 12, 2017
  • 3 replies
  • 3178 views

There are 4 ypes of garbage collector in java 1.8.

1. Serial

2. Parallel

3. CMS

4. G1

Default is parallel GC. Any recommendation which GC type should we use in AEM.

Also are there any recommendation regarding JVM paramaters that we should be using in AEM?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by MC_Stuff

Hi Sandeep,

You need tune based on you application, Most commonly used for small/medium apps at CQ-OPS - JVM init Arguments for a Reliable CQ Instance

Thanks,

3 replies

MC_Stuff
MC_StuffAccepted solution
Level 10
June 13, 2017

Hi Sandeep,

You need tune based on you application, Most commonly used for small/medium apps at CQ-OPS - JVM init Arguments for a Reliable CQ Instance

Thanks,

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
June 14, 2017

Please also check JVM tuning or premature optimization? | Things on a content management system

edgarn27224967
edgarn27224967
June 16, 2017

Many of these recommendations - like many JVM argument recommendations - are old.  Even the quite old recommendation of setting the minimum and maximum heap size is not necessarily a performance enhancer from what I've read on the intertubes. Though one does have to set the max heap size if one wants it to be able to get bigger than the built in default.

Ideally one sets these by testing and tuning, but obviously many people/sites don't have the time to do much in the way of this and the JVM has quite a few possible arguments and often little or no explanation of their function. At this point, with java 8 I'm setting fewer arguments and letting it determine what to do as much as possible which has worked surprisingly well. The G1C1 GC seems to work well on the sites I've seen with it.

Terms & ConditionsAccessibility statement

Loading footer...