eden++java,一次FullGC，避免新生代（Eden+Survivor）的内容全部放到老年代-CSDN博客

本文详细解析了Java应用程序在运行过程中遇到的内存管理问题，包括堆内存的使用情况、垃圾回收机制的工作原理及其对系统性能的影响。通过对具体案例的分析，展示了如何通过ParNew和CMS垃圾收集器来解决内存溢出问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

{Heap before GC invocations=619 (full 8): par new generation total 3263424K, used 3086970K [0x0000000680400000, 0x000000075d900000, 0x000000075d900000) eden space 2900864K, 100% used [0x0000000680400000, 0x00000007314e0000, 0x00000007314e0000) from space 362560K, 51% used [0x00000007476f0000, 0x0000000752cae980, 0x000000075d900000) to space 362560K, 0% used [0x00000007314e0000, 0x00000007314e0000, 0x00000007476f0000) concurrent mark-sweep generation total 1612800K, used 961309K [0x000000075d900000, 0x00000007c0000000, 0x00000007c0000000) Metaspace used 210744K, capacity 222745K, committed 222808K, reserved 1249280K class space used 20218K, capacity 22236K, committed 22268K, reserved 1048576K

2019-11-13T03:36:46.611+0800: 14568.064: [GC (Allocation Failure) 14568.064: [ParNew (promotion failed): 3086970K->3081843K(3263424K), 0.4982995 secs]14568.562: [CMS: 961884K->215158K(1612800K), 1.1328686 secs] 4048279K->215158K(4876224K), [Metaspace: 210744K->210744K(1249280K)], 1.6315216 secs] [Times: user=1.67 sys=0.03, real=1.64 secs]

Heap after GC invocations=620 (full 9)Connection Reset By Peer

par new generation total 3263424K, used 0K [0x0000000680400000, 0x000000075d900000, 0x000000075d900000)

eden space 2900864K, 0% used [0x0000000680400000, 0x0000000680400000, 0x00000007314e0000)

from space 362560K, 0% used [0x00000007314e0000, 0x00000007314e0000, 0x00000007476f0000)

to space 362560K, 0% used [0x00000007476f0000, 0x00000007476f0000, 0x000000075d900000)

concurrent mark-sweep generation total 1612800K, used 215158K [0x000000075d900000, 0x00000007c0000000, 0x00000007c0000000)

Metaspace used 210701K, capacity 222685K, committed 222808K, reserved 1249280K

class space used 20213K, capacity 22226K, committed 22268K, reserved 1048576K

}复制