GC的时机
在分代模型的基础上,GC从时机上分为两种:Scavenge GC 和 Full GC
Scavenge GC (Mionr GC)
触发时机:新对象生成时,Eden空间满了
理论上Eden区大多数对象会在Scavenge GC 回收,复制算法的执行效率会很高,Scavenge GC时间比较短
Full GC
整个jvm进行整理,包括Young、old和perm
主要触发时机:old满了 perm满了 system.gc()
效率很低,尽量减少Full GC
配置jvm 参数如下:
-verbose:gc 打印垃圾收集的情况
-Xms20M 最小堆大小
-Xmx20M 最大堆大小
-Xmn10M 新生代大小
-XX:+PrintGCDetails 打印GC收集详细信息
-XX:SurvivorRatio=8 eden 与 from survivor to survivor 比例 8:1:1
public static void main(String[] args) {
int size = 1024 * 1024;
byte[] myAlloc1 = new byte[2*size];
byte[] myAlloc2 = new byte[2*size];
byte[] myAlloc3 = new byte[2*size];
byte[] myAlloc4 = new byte[2*size];
System.out.println("Test1.main");
}
打印结果:
GC (Allocation Failure): Eden满了 分配失败进行GC垃圾回收
PSYoungGen: 表述 使用parallel Scavenge 收集器
ParOldGen:表示 parallel old 老年代收集器
6874K->992K(9216K) : 6874K表示回收之前存活对象在新生代的空间的容量,992K表示回收后存活对象的容量
9216K:表示新生代总空间容量大小
6874K->3337K(19456K):6874K表示对象总的堆大小,3337K执行完回收之后 存活对象总的堆大的大小
PSYoungGen:表示新生代
ParOldGen :老年代
6874-992 = 5882 //执行完GC后,新生代释放的空间的容量,新生代释放的空间 :1)被回收 2)晋升到老年代
6874-3337=3537 //执行完GC后,总的堆空间释放的容量
5882-3537=2345 //等于ParOldGen 老年代容量
[GC (Allocation Failure) [PSYoungGen: 6874K->992K(9216K)] 6874K->3337K(19456K), 0.0042664 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
Test1.main
Heap
PSYoungGen total 9216K, used 7458K [0x00000000ff600000, 0x0000000100000000, 0x0000000100000000)
eden space 8192K, 78% used [0x00000000ff600000,0x00000000ffc50848,0x00000000ffe00000)
from space 1024K, 96% used [0x00000000ffe00000,0x00000000ffef8188,0x00000000fff00000)
to space 1024K, 0% used [0x00000000fff00000,0x00000000fff00000,0x0000000100000000)
ParOldGen total 10240K, used 2345K [0x00000000fec00000, 0x00000000ff600000, 0x00000000ff600000)
object space 10240K, 22% used [0x00000000fec00000,0x00000000fee4a608,0x00000000ff600000)
Metaspace used 3304K, capacity 4496K, committed 4864K, reserved 1056768K
class space used 359K, capacity 388K, committed 512K, reserved 1048576K
public static void main(String[] args) {
int size = 1024 * 1024;
byte[] myAlloc1 = new byte[2*size];
byte[] myAlloc2 = new byte[2*size];
byte[] myAlloc3 = new byte[2*size];
byte[] myAlloc4 = new byte[2*size];
byte[] myAlloc5 = new byte[2*size];
System.out.println("Test1.main");
}
打印结果:
Full GC (Ergonomics):会带来stop the world 让业务线程暂停
PSYoungGen: 1008K->0K(9216K):新生代回收后为0
ParOldGen: 8513K->9157K(10240K):老年代回收后,容量变多了,因为新生代一部分数据进入老年代
[GC (Allocation Failure) [PSYoungGen: 6874K->1016K(9216K)] 6874K->3361K(19456K), 0.0040588 secs] [Times: user=0.03 sys=0.02, real=0.00 secs]
[GC (Allocation Failure) [PSYoungGen: 7315K->1008K(9216K)] 9661K->9521K(19456K), 0.0063014 secs] [Times: user=0.00 sys=0.00, real=0.01 secs]
[Full GC (Ergonomics) [PSYoungGen: 1008K->0K(9216K)] [ParOldGen: 8513K->9157K(10240K)] 9521K->9157K(19456K), [Metaspace: 3296K->3296K(1056768K)], 0.0090750 secs] [Times: user=0.03 sys=0.00, real=0.01 secs]
Test1.main
Heap
PSYoungGen total 9216K, used 2270K [0x00000000ff600000, 0x0000000100000000, 0x0000000100000000)
eden space 8192K, 27% used [0x00000000ff600000,0x00000000ff837838,0x00000000ffe00000)
from space 1024K, 0% used [0x00000000fff00000,0x00000000fff00000,0x0000000100000000)
to space 1024K, 0% used [0x00000000ffe00000,0x00000000ffe00000,0x00000000fff00000)
ParOldGen total 10240K, used 9157K [0x00000000fec00000, 0x00000000ff600000, 0x00000000ff600000)
object space 10240K, 89% used [0x00000000fec00000,0x00000000ff4f1430,0x00000000ff600000)
Metaspace used 3304K, capacity 4496K, committed 4864K, reserved 1056768K
class space used 359K, capacity 388K, committed 512K, reserved 1048576K
Process finished with exit code 0
public static void main(String[] args) {
int size = 1024 * 1024;
byte[] myAlloc1 = new byte[8*size];
System.out.println("Test1.main");
}
打印结果:
虚拟机分配过程,当对象创建时先进入新生代空间,当新生代空间满时,新创建的对象将直接进入到老年代。
Test1.main
Heap
PSYoungGen total 9216K, used 4992K [0x00000000ff600000, 0x0000000100000000, 0x0000000100000000)
eden space 8192K, 60% used [0x00000000ff600000,0x00000000ffae0370,0x00000000ffe00000)
from space 1024K, 0% used [0x00000000fff00000,0x00000000fff00000,0x0000000100000000)
to space 1024K, 0% used [0x00000000ffe00000,0x00000000ffe00000,0x00000000fff00000)
ParOldGen total 10240K, used 8192K [0x00000000fec00000, 0x00000000ff600000, 0x00000000ff600000)
object space 10240K, 80% used [0x00000000fec00000,0x00000000ff400010,0x00000000ff600000)
Metaspace used 3302K, capacity 4496K, committed 4864K, reserved 1056768K
class space used 359K, capacity 388K, committed 512K, reserved 1048576K
java -XX:+PrintCommandLineFlags -version 打印jvm启动参数以及java版本号
java -XX:+PrintCommandLineFlags -version
-XX:InitialHeapSize=132269760 -XX:MaxHeapSize=2116316160 -XX:+PrintCommandLineFlags -XX:+UseCompressedClassPointers -XX:+UseCompressedOops -XX:-UseLargePagesIndiv
idualAllocation -XX:+UseParallelGC
java version "1.8.0_91"
Java(TM) SE Runtime Environment (build 1.8.0_91-b15)
Java HotSpot(TM) 64-Bit Server VM (build 25.91-b15, mixed mode)
InitialHeapSize 等价于
Xms MaxHeapSize 等价于 Xmx
默认GC UseParallelGC : 1) parallel old 老年代收集器 2)parallel Scavenge 新生代收集器
配置jvm 参数如下:
-verbose:gc
-Xms20M
-Xmx20M
-Xmn10M
-XX:+PrintGCDetails
-XX:SurvivorRatio=8
-XX:PretenureSizeThreshold=4194304 当我们创建的对象大小,超过指定的大小,那么它不会在新生代中分配,而是直接去老年代中分配 并且它需要和 串行收集器 一起使用才会生效
-XX:UseSerialGC
public static void main(String[] args) {
int size = 1024 * 1024;
byte[] myAlloc1 = new byte[5*size];
System.out.println("Test1.main");
}
打印结果:
可以看出我们配置PretenureSizeThreshold:4M大小,创建一个5M对象,并且在串行收集器下,直接分配到老年代中
Test2.main
Heap
def new generation total 9216K, used 4992K [0x00000000fec00000, 0x00000000ff600000, 0x00000000ff600000)
eden space 8192K, 60% used [0x00000000fec00000, 0x00000000ff0e0370, 0x00000000ff400000)
from space 1024K, 0% used [0x00000000ff400000, 0x00000000ff400000, 0x00000000ff500000)
to space 1024K, 0% used [0x00000000ff500000, 0x00000000ff500000, 0x00000000ff600000)
tenured generation total 10240K, used 5120K [0x00000000ff600000, 0x0000000100000000, 0x0000000100000000)
the space 10240K, 50% used [0x00000000ff600000, 0x00000000ffb00010, 0x00000000ffb00200, 0x0000000100000000)
Metaspace used 3302K, capacity 4496K, committed 4864K, reserved 1056768K
class space used 359K, capacity 388K, committed 512K, reserved 1048576K
配置jvm 参数如下:
* -verbose:gc * -Xms20M * -Xmx20M * -Xmn10M * -XX:+PrintGCDetails * -XX:SurvivorRatio=8 * -XX:MaxTenuringThreshold=5 * -XX:+PrintTenuringDistribution
MaxTenuringThreshold 作用:在可以自动调节对象晋升到老年代阈值的gc中,设置该阈值的最大值;该参数的默认值为15,cms中默认值为6,g1中默认值为15 经历了多次gc后,存活的对象会在form survivor 与 to survivor 之间来回存放,而这里面的一个前提是这两个空间有足够的大小来存放这些数据,在gc算法中,会计算每个对象年龄的大小,如果达到某个年龄后发现总大小已经大于了survivor空间的50%,那么这时就需要调整阈值,不能等到默认的15次 才完成晋升,这样会导致survivor空间不足,所以需要调整阈值,让这些存活对象尽快完成晋升