- 浏览: 431920 次
- 性别:
- 来自: 深圳
-
文章分类
最新评论
-
Glogo:
楼主您好,我在试验您的代码的时候发现新开的三个子线程并没有一直 ...
java 高并发 ReentrantLock -- 可重入的锁 -
univasity:
最近发觉也被限速了,投诉一下就好一会~~ 看来明天又要和电信M ...
ADSL上网速度慢 都是帐号限速惹的祸 -
liuyuanhui0301:
java 高并发 ReentrantLock -- 可重入的锁 -
dang_java:
呵.很好的说明文档.
JXTA技术与应用发展 -
helloqidi:
谢谢,学习了
SQL中exists和in的区别
The original article is at : http://prefetch.net/blog/index.php/2008/01/16/monitoring-garbage-collection-with-jstat/
Java memory management revolves around the garbage collector, which is the entity responsible for traversing the heap and freeing space that is being taken up by unreferenced objects. Garbage collection makes life easier for Java programmers, since it frees them from having to explicitly manage memory resources (this isn’t 100% true, but close enough). In the Java runtime environment, there are two types of collections that can occur. The first type of collection is referred to as minor collection. Minor collections are responsible for locating live objects in the young generation (eden), copying these objects to the inactive survivor space, and moving tenured objects from the active survivor space to the old (tenured) generation (this assumes that a generational collector is being used). The second form of collection is the major collection. This type of collection frees unreferenced objects in in the tenured generation, and optionally compacts the heap to reduce fragmentation.
When debugging performance problems, it is extremely useful to be able to monitor object allocations and frees in the new and old generations. The Java development kit comes with the jstat utility, which provides a ton of visibility into what the garbage collector is doing, as well as a slew of information on how each generation is being utilized. To use jstat to display garbage collection statistics for the new, old and permanent generations, jstat can be invoked with the “-gc” (print garbage collection heap statistics) option, the “-t” (print the total number of seconds the JVM has been up) option, the process id to retrieve statistics from, and an optional interval to control how often statistics are printed:
$ jstat -gc -t `pgrep java` 5000
Timestamp S0C S1C S0U S1U EC EU OC OU PC PU YGC YGCT FGC FGCT GCT 98772.0 1600.0 1600.0 0.0 1599.8 13184.0 5561.6 245760.0 201671.9 16384.0 6443.0 166683 2402.690 32411 110.564 2513.255 98777.0 1600.0 1600.0 1599.4 0.0 13184.0 9533.7 245760.0 156797.1 16384.0 6443.0 166690 2402.785 32414 110.573 2513.359 98782.0 1600.0 1600.0 1599.7 0.0 13184.0 10328.6 245760.0 166402.2 16384.0 6443.0 166698 2402.889 32416 110.580 2513.469 98787.0 1600.0 1600.0 0.0 1599.9 13184.0 2383.5 245760.0 195366.0 16384.0 6443.0 166707 2403.016 32416 110.580 2513.595
The output above contains the size of each survivor space (S0C && S1C), the utilization of each survivor space (S0U && S1U), the capacity of eden (EC), the utilization of eden (EU), the capacity of the old generation (OC), the utilization of the old generation (OU), the permanent generation capacity (PC), the permanent generation utilization (PU), the total number of young generation garbage collection events (YGC), the total amount of time spent collecting objects in the new generation (YGCT), the total number of old generation garbage collection events that have occurred (FGC), the total amount of time spent collecting objects in the old generation (FGCT), and the total time spent performing garbage collection.
If you prefer to view garbage collection events as percentages, you can use the “-gcutil” option:
$ jstat -gcutil -t -h5 `pgrep java` 5000
Timestamp S0 S1 E O P YGC YGCT FGC FGCT GCT 99814.1 0.00 99.99 18.08 63.77 39.32 168551 2427.512 32800 111.800 2539.313 99819.1 99.96 0.00 66.29 78.18 39.32 168562 2427.649 32800 111.800 2539.449 99824.1 100.00 0.00 94.40 62.46 39.32 168572 2427.795 32803 111.815 2539.610 99829.2 100.00 0.00 60.25 65.08 39.32 168580 2427.888 32806 111.824 2539.713
The output above contains the utilization of each survivor space as a percentage of the total survivor space capacity (S0 && S1), the utilization of eden as a percentage of the total eden capacity (E), the utilization of the tenured generation as a percentage of the total tenured generation capacity (O), the utilization of the permanent generation as a percentage of the total permanent generation capacity (P), the total number of young generation garbage collection events (YGC), the total time spent collection objects in the young generation (YGCT), the total number of of old generation garbage collection events (FGC), the total amount of time spent collecting objects in the old generation (FGCT), and the total garbage collection time.
To get the time spent in garbage collection along with the reason the collection occurred, jstat can be run with the “-gccause” option:
$ jstat -gccause -t `pgrep java` 1000
Timestamp S0 S1 E O P YGC YGCT FGC FGCT GCT LGCC GCC 100157.3 99.96 0.00 66.27 63.82 39.32 169160 2435.394 32925 112.202 2547.595 CMS Initial Mark No GC 100158.3 0.00 99.99 32.14 67.72 39.32 169163 2435.430 32925 112.202 2547.631 unknown GCCause No GC 100159.3 0.00 99.97 50.22 65.10 39.32 169165 2435.454 32927 112.208 2547.662 CMS Initial Mark No GC 100160.3 99.97 0.00 6.02 62.46 39.32 169168 2435.493 32928 112.211 2547.704 unknown GCCause No GC 100161.3 99.97 0.00 32.14 62.46 39.32 169168 2435.493 32928 112.211 2547.704 unknown GCCause No GC
There are also options to print class loader activity and hotspot compiler statistics, and to break down utilization by generation (this is extremely useful when your trying to profile a specific memory pool). There are a number of incredibly useful opensource tools for visualizing garbage collection data, and I hope to talk about these in the near future.
发表评论
-
JVM 深入笔记
2012-04-12 20:36 1026JVM 深入笔记(1)内存区域是如何划分的? 一个超短的前言 ... -
JVM启动参数
2011-06-10 16:27 975java [jvmargs] class [arguments ... -
JVM指令集 和 一个异常例子
2011-05-19 16:14 1028指令码 助记符 说明 0x00 nop ... -
The Top Java Memory Problems – Part 1
2011-05-18 11:01 915转载:http://blog.dynatrace.com/20 ... -
BTrace使用简介
2011-04-19 13:51 787该文转载自:http://rdc.taobao.com/tea ... -
大方法的执行性能与调优过程小记
2011-04-18 16:20 813该文章转载自:http://rdc.taobao.com/te ... -
十个最好的Java性能故障排除工具
2011-04-18 16:02 942推荐十个最好的Java性能 ... -
两个OOM Cases排查过程的分享
2011-04-18 15:39 944分享一下两个OOM Cases的查找过程,一个应用是Nativ ... -
理解Heap Profling名词-Shallow和Retained Sizes
2011-04-18 14:58 987所有包含Heap Profling功能的工具(MAT, You ... -
Java深度历险(四)——Java垃圾回收机制与引用类型
2011-04-01 08:18 1010Java语言的一个重要特性 ... -
Thread Dump 和Java应用诊断
2011-03-30 08:08 1139Thread Dump 和Java应用诊断 ... -
Memory Analysis Part 1 – Obtaining a Java Heapdump
2011-03-14 16:06 1132For troubleshooting Java memory ... -
Java Memory Leaks et al. (2. Act)
2011-03-14 15:37 935The first act of this blog-seri ... -
Erlang memory architecture vs Java memory architecture
2011-03-14 15:36 921I read a really, really interes ... -
The Java Memory Architecture (1. Act)
2011-03-14 15:15 1425One of the biggest strength of ... -
Permanent generation
2011-03-14 14:53 1311版权声明:转载时请以 ... -
JVM内存模型以及垃圾回收
2011-03-13 09:38 1007内存由 Perm 和 Heap 组成. 其中 Heap ... -
Java虚拟机垃圾回收机制
2011-03-13 09:31 864一、相关概念 基本 ... -
JVM结构
2011-03-10 14:43 899类文件格式 JVM使用一 ... -
OOM与JVM(转)
2009-03-24 15:49 1004OOM与JVM(转) 2008年08月08日 星期五 15: ...
相关推荐
它整合了多个Java诊断工具,如JConsole、jstat、jinfo、jstack和jmap等,提供了一系列功能,包括: 1. **生成和分析堆内存的dump**:当应用遇到内存问题时,VisualVM可以生成heap dump文件,通过分析这些文件,...
2. **垃圾收集日志(Garbage Collection Logging)**:通过配置JVM启动参数,如-XX:+PrintGCDetails,可以获取垃圾收集器详细的活动记录。这些信息有助于分析应用程序的内存使用情况,判断是否存在内存泄漏或频繁的...
在众多的JVM调优工具中,`jstat`(Java Virtual Machine Statistics Monitoring Tool)是一个非常实用的命令行工具,尤其适用于实时监控和分析JVM的状态。 一、`jstat` 命令详解 `jstat`命令允许开发者查看JVM的...
6. **GC(Garbage Collection)调优**:Java的自动内存管理依赖于垃圾收集器,但过度的GC活动会影响应用性能。了解不同类型的GC策略(如Serial、Parallel、Concurrent Mark Sweep和G1)并进行调优,对于提升应用性能...
###### 1.7.1.2 Using HPjmeter to Analyze Garbage Collection Data (使用HPjmeter分析垃圾回收数据) - **功能**:监视垃圾回收过程,确保内存管理高效。 - **应用场景**:对于频繁发生GC暂停的应用来说尤其重要。 ...