Constant garbage collection Java -

After

I check my application log and the following:

  163.029: [GC163.029 [ParNew: 545354K-> 8K (613440K), 0.0421560 secs] 547578K- & gt; 2232K (20903424K), 0.0422630 secs [Times: user = 0.27 sys = 0.03, real = 0.04 sec] 164.014: [GC164.014: [ParNew: 545352K-> 6K (613440K), 0.0438010 secs] 547576K-> 2230K (20903424K), 0.043 9 220 seconds] [Times: user = 0.30ss = 0.00, real = 0.04 secs] 164.995: [GC164.996 [ParNew: 545350K- & gt; 10K (613440K), 0.0350310 secs] 547574K-> 2234K (20903424K), 0.0351570 secs [Times: user = 0.27 sys = 0.00, real = 0.04 sec] 165.967: [GC165.967: [ParNew: 545354K-> 8K (613440K), 0.0532350 secs] 547578K- & gt; 2232K (20903424K), 0.0533560 secs [Times: user = 0.39 sys = 0.00, real = 0.06 sec] 166.946: [GC166.946: [ParNew: 545352K-> 10K (613440K), 0.0308 9 30 seconds] 547576K-> 2234K (20903424K), 0.030 99 80 sec] [Times: user = 0.25 sys = 0.00, real = 0.03 sec] 167.919: [GC167.919: [ParNew: 545354K -> 12K (of 613440), 0.0393180 seconds] 547578K-> 2236K (20903424K), 0.03 9 4180 seconds] [Times: user = 0.30 sys = 0.00, real = 0.04 sec] 168.890: [GC168.890: [ParNew: 545356K-> 4K (613440K), 0.044 9 310 secs] 547580K - & gt; 2230K (20903424K), 0.0450500 secs [Times: user = 0.31 sys = 0.00, real = 0.04 sec] 169.869: [GC169.869: [ParNew: 545348K-> 4K (613440K), 0.0422740 second] 547574K-> 2230K (20903424K), 0.0423800 secs [Times: user = 0.26 sys = 0.02, real = 0.04 sec] 170.850: [GC170.850: [ParNew: 545348K-> 4K (613440K), 0.0434500 secs) 547574K-> 2230K (20903424K), 0.04,35,570 secs [Times: user = 0.31ss = 0.00, real = 0.04 seconds]  

Too many enough memory (I only 2.6% memory Is available)

What could be the reason for such behavior? + UseConcMarkSweepGC -XX :: + PrintGCDetails -XX: + PrintGCTimeStamps Jar

  Java-Xss515m-Xms20g -Xmx20g -XX 
 
 
 
 Given that the hotspot uses one, normal garbage collection is normal and harmless. This is the reason that just means that the Eden generation space has ended and is being collected, which is usually very fast - Quite unnoticeable 
 
 The frequency of garbage collection, therefore, is mostly related to its allocation  bandwidth , instead of the amount of memory in use, the mistake is thinking that it is something bad , While in fact it is how GC intends to design and work.