So, by default the start script of AEM doesn't contain any specific JVM OPTS that configure / tune the way in which the JVM performs Garbage Collection.
Just wondering: What JAVA_OPTS do you guys use in the start script to configure the GC process for the Java Virtual Machine?
PS: Not talking about the Garbage Collection for the Datastore, this is about the JVM and it's memory management.
PSS: How about using the new G1GC, anyone got experience with that?
Solved! Go to Solution.
Views
Replies
Total Likes
Why do you want to change JVM settings if you don't have to?
JVM tuning or premature optimization? | Things on a content management system
Views
Replies
Total Likes
Any issues with your JVM that force you to change GC OPTS?
Views
Replies
Total Likes
We're seeing a lot of heap memory being held in the Old Gen Space. Manually triggering a Full GC reduces this by a lot. My assumption at this point is that GC is set a bit to lazy by default.
We've assigned 12Gb to the heap by the way, so in any case there's plenty of room left.
Views
Replies
Total Likes
Why do you want to change JVM settings if you don't have to?
JVM tuning or premature optimization? | Things on a content management system
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies