I think that on large heap is suggested to monitor the garbage
collection behavior and try to add a strategy adapted to your
performance. On my production environment with a heap of 6 GB I set
this parameter (server with 8 cores):
-server -Xms6144m -Xmx6144m -XX:MaxPermSize=512m
-Dcom.sun.management.jmxremote -XX:+UseParNewGC -XX:+UseConcMarkSweepGC
-XX:+CMSIncrementalMode -XX:+CMSParallelRemarkEnabled
-XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=70
-XX:ConcGCThreads=6 -XX:ParallelGCThreads=6
Marcello
On 07/24/2014 03:53 PM, Ameya Aware wrote:
I did not make any other change than this.. rest of the settings are
default.
Do i need to set garbage collection strategy?
On Thu, Jul 24, 2014 at 9:49 AM, Marcello Lorenzi <mlore...@sorint.it
<mailto:mlore...@sorint.it>> wrote:
Hi,
Did you set a Garbage collection strategy on your JVM ?
Marcello
On 07/24/2014 03:32 PM, Ameya Aware wrote:
Hi
I am in process of indexing around 2,00,000 documents.
I have increase java jeap space to 4 GB using below command :
java -Xmx4096M -Xms4096M -jar start.jar
Still after indexing around 15000 documents it gives java heap
space error
again.
Any fix for this?
Thanks,
Ameya
