Java Profiling Tools

Proﬁlers
Ferramentas de Monitoração

Sunday, June 27, 2010

Objetivo

Compreender os principais conceitos de proﬁling
de código e o funcionamento das ferramentas
mais relevantes do mundo Java EE.

3

Proﬁlers deveriam ser ferramentas de
uso das equipes de desenvolvimento.

4

Proﬁlers são ferramentas usadas pelas equipes
de infra-estrutura para se protegerem de
maus códigos.

5

HPROF
Heap Profiler

The Heap Profiler (HPROF) tool is a simple profiler
agent shipped with the JDK release.(...)The HPROF
tool is capable of presenting CPU usage, heap
allocation statistics, and monitor contention profiles. In
addition, it can report complete heap dumps and
states of all the monitors and threads in the Java
virtual machine. In terms of diagnosing problems,
HPROF is useful when analyzing performance, lock
contention, memory leaks, and other issues.

http://java.sun.com/javase/6/webnotes/trouble/TSG-VM/html/tooldescr.html#gblvj 6

$ java -agentlib:hprof=help
HPROF: Heap and CPU Profiling Agent (JVMTI Demonstration Code)

hprof usage: java -agentlib:hprof=[help]|[<option>=<value>, ...]

Option Name and Value Description Default
--------------------- ----------- -------
heap=dump|sites|all heap profiling all
cpu=samples|times|old CPU usage off
monitor=y|n monitor contention n
format=a|b text(txt) or binary output a
file=<file> write data to file java.hprof[{.txt}]
net=<host>:<port> send data over a socket off
depth=<size> stack trace depth 4
interval=<ms> sample interval in ms 10
cutoff=<value> output cutoff point 0.0001
lineno=y|n line number in traces? y
thread=y|n thread in traces? n
doe=y|n dump on exit? y
msa=y|n Solaris micro state accounting n
force=y|n force output to <file> y
verbose=y|n print messages about dumps y
...

7

Regra geral

java -agentlib:hprof=... NomeDaClasse

Ctrl+C Ctrl+
shutdown

java.hprof.txt
8

$ JVM_ARGS="-agentlib:hprof=heap=sites" ./jmeter.sh

THREAD START (obj=50000143, id = 200001, name="main", group="main")
THREAD START (obj=500013d1, id = 200004, name="Java2D Disposer", group="system")
THREAD START (obj=5000191f, id = 200005, name="AWT-XAWT", group="main")
THREAD START (obj=5000195f, id = 200006, name="Image Fetcher 0", group="main")
...
THREAD END (id = 200008)
...
TRACE 300000:
! <empty>
TRACE 300001:
! java.lang.Thread.<init>(Thread.java:432)
TRACE 300002:
TRACE 300003:
! java.lang.String.toCharArray(String.java:2726)
! java.lang.Thread.init(Thread.java:349)
....
SITES BEGIN (ordered by live bytes) Wed May 27 07:34:16 2009
percent live alloc'ed stack class
rank self accum bytes objs bytes objs trace name
1 9,88% 9,88% 2486200 3 2486200 3 317684 int[]
2 2,13% 12,01% 535440 6693 535760 6697 310354 javax.swing.text.html.InlineView
3 2,07% 14,08% 521592 159 623912 168 306967 char[]
4 1,78% 15,86% 447696 18654 450672 18778 305960 java.awt.Rectangle
5 1,72% 17,58% 432240 18010 599808 24992 310036 java.util.Hashtable$Entry
java.hprof.txt
9

$ JVM_ARGS="-agentlib:hprof=heap=dump" ./jmeter.sh

...
OBJ 50036a21 (sz=24, trace=309881, class=javax.swing.text.html.StyleSheet
$SmallConversionSet@5000e518)
! attributes! 50036a22
! this$0! ! 5000b0d6
! this$0! ! 5000b0d6
ARR 50036a22 (sz=32, trace=309882, nelems=4, elem type=java.lang.Object[]@500000a0)
! [0]! ! 5000da97
! [1]! ! 50065782
! [2]! ! 50007706
! [3]! ! 5000dae2
OBJ 50036a23 (sz=40, trace=310897, class=javax.swing.text.html.HTMLDocument$BlockElement@5000f3eb)
! parent! ! 50036901
! attributes! 500107d4
! this$0! ! 5000b16d
! children!50031212
! this$0! ! 5000b16d
! this$0! ! 5000b16d
OBJ 50036a24 (sz=392, trace=306854, class=javax.swing.JLabel@50000868)
OBJ 50036a25 (sz=8, trace=306855, class=java.lang.Object@5000009f)
OBJ 50036a27 (sz=24, trace=300098, class=java.util.ArrayList@5000005b)
OBJ 50036a29 (sz=16, trace=306857, class=javax.swing.event.EventListenerList@50002745)
OBJ 50036a2a (sz=24, trace=306356, class=java.lang.ref.WeakReference@50000037)
...

java.hprof.txt

10
9

$ JVM_ARGS="-agentlib:hprof=cpu=samples" ./jmeter.sh

...
CPU SAMPLES BEGIN (total = 1564) Wed May 27 07:38:42 2009
rank self accum count trace method
1 48,47% 48,47% 758 300482 sun.awt.X11.XToolkit.waitForEvents
2 2,56% 51,02% 40 300104 java.lang.ClassLoader.defineClass1
3 1,15% 52,17% 18 300001 java.lang.ClassLoader.findBootstrapClass
4 1,09% 53,26% 17 301617 sun.awt.X11.XInputMethod.openXIMNative
5 0,77% 54,03% 12 300513 java.util.zip.Inflater.inflateBytes
6 0,77% 54,80% 12 300778 java.awt.EventQueue.postEventPrivate
7 0,77% 55,56% 12 300834 sun.font.FileFont.getGlyphImage
8 0,70% 56,27% 11 301388 java.lang.Class.forName0
...
java.hprof.txt

11

$ JVM_ARGS="-agentlib:hprof=cpu=samples" ./jmeter.sh

...
CPU SAMPLES BEGIN (total = 1564) Wed May 27 07:38:42 2009
1 48,47% 48,47% 758 300482 sun.awt.X11.XToolkit.waitForEvents
2 2,56% 51,02% 40 300104 java.lang.ClassLoader.defineClass1
3 1,15% 52,17% 18 300001 java.lang.ClassLoader.findBootstrapClass
4 1,09% 53,26% 17 301617 sun.awt.X11.XInputMethod.openXIMNative
5 0,77% 54,03% 12 300513 java.util.zip.Inflater.inflateBytes
6 0,77% 54,80% 12 300778 java.awt.EventQueue.postEventPrivate
7 0,77% 55,56% 12 300834 sun.font.FileFont.getGlyphImage
8 0,70% 56,27% 11 301388 java.lang.Class.forName0
...
java.hprof.txt

amostragem

11

$ JVM_ARGS="-agentlib:hprof=cpu=times" ./jmeter.sh

...
CPU TIME (ms) BEGIN (total = 1743936) Wed May 27 07:44:33 2009
1 16,23% 16,23% 458 306106 java.lang.ref.ReferenceQueue.remove
2 16,21% 32,44% 40 306095 java.lang.Object.wait
4 14,79% 63,42% 1 393892 java.util.TimerThread.mainLoop
6 2,97% 74,07% 37 312015 sun.awt.image.ImageFetcher.nextImage
...
java.hprof.txt

12

$ JVM_ARGS="-agentlib:hprof=cpu=times" ./jmeter.sh

...
CPU TIME (ms) BEGIN (total = 1743936) Wed May 27 07:44:33 2009
4 14,79% 63,42% 1 393892 java.util.TimerThread.mainLoop
6 2,97% 74,07% 37 312015 sun.awt.image.ImageFetcher.nextImage
...
java.hprof.txt

valores exatos

12

$ export JAVA_OPTS="-agentlib:hprof=monitor=y"
$ ./catalina.sh run java.hprof.txt
THREAD START (obj=5000013e, id = 200001, name="main", group="main")
WAIT: MONITOR Ljava/lang/ref/Reference$Lock;, timeout=0, thread 200003
WAIT: MONITOR Ljava/lang/ref/ReferenceQueue$Lock;, timeout=0, thread 200004
WAITED: MONITOR Ljava/lang/ref/Reference$Lock;, time_waited=678, thread 200003
WAIT: MONITOR Ljava/lang/ref/Reference$Lock;, timeout=0, thread 200003
WAITED: MONITOR Ljava/lang/ref/ReferenceQueue$Lock;, time_waited=677, thread 200004
WAIT: MONITOR Ljava/lang/ref/ReferenceQueue$Lock;, timeout=0, thread 200004
WAITED: MONITOR Ljava/lang/ref/Reference$Lock;, time_waited=117, thread 200003
...
MONITOR DUMP BEGIN
THREAD 200001, trace 300804, status: native|R
THREAD 200002, trace 300000, status: ZO
THREAD 200003, trace 300210, status: CW
THREAD 200004, trace 300212, status: CW
THREAD 200006, trace 300805, status: SL
THREAD 200007, trace 300000, status: ZO
...
MONITOR Ljava/net/SocksSocketImpl;
! owner: thread 200001, entry count: 1
! waiting to enter:
! waiting to be notified:
MONITOR Ljava/lang/Shutdown$Lock;
! waiting to enter:
MONITOR Ljava/lang/Class;
! waiting to enter:
MONITOR DUMP END 13

jboss-4.2.2.GA/bin $ tail -3 run.conf
# Ativacao do HPROF
JAVA_OPTS="$JAVA_OPTS -agentlib:hprof=cpu=samples,file=jboss.hprof.txt"

jboss-4.2.2.GA/bin $ ./run.sh
=========================================================================

JBoss Bootstrap Environment Parâmetro
conﬁgurado no
JBOSS_HOME: /Users/alegomes/jbtun/app/jboss-4.2.2.GA
JBoss...
JAVA: /Library/Java/Home/bin/java

JAVA_OPTS: -Dprogram.name=run.sh -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -
Dsun.rmi.dgc.server.gcInterval=3600000 -Dcom.sun.management.jmxremote -
Djboss.platform.mbeanserver -
Djavax.management.builder.initial=org.jboss.system.server.jmx.MBeanServerBuilderImpl -
agentlib:hprof=cpu=samples,file=jboss.hprof.txt

CLASSPATH: /Users/alegomes/jbtun/app/jboss-4.2.2.GA/bin/run.jar

=========================================================================

08:36:39,356 INFO [Server] Starting JBoss (MX MicroKernel)...
08:36:39,368 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA
date=200710221139)
...
08:38:53,308 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
08:38:53,402 INFO [Server] JBoss (MX MicroKernel) [4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA
date=200710221139)] Started in 2m:13s:890ms
...mas nada demais aconteceu. 14

Ctrl +

jboss.hprof.txt
15

java.hprof.txt
JAVA PROFILE 1.0.1, created Wed May 27 07:33:19 2009

Header for -agentlib:hprof (or -Xrunhprof) ASCII Output (JDK 5.0 JVMTI based)

@(#)jvm.hprof.txt! 1.5 06/01/28

Copyright (c) 2006 Sun Microsystems, Inc. All Rights Reserved.

WARNING! This file format is under development, and is subject to
change without notice.

This file contains the following types of records:

...

documentação no
próprio arquivo
gerado
16

THREAD START
THREAD END mark the lifetime of Java threads

THREAD START (obj=5000013f, id = 200001, name="main", group="main")
THREAD START (obj=5000013f, id = 200005, name="Java2D Disposer", group="system")
THREAD START (obj=5000013f, id = 200006, name="AWT-XAWT", group="main")
THREAD START (obj=5000013f, id = 200010, name="AWT-Shutdown", group="main")
THREAD START (obj=500005e7, id = 200011, name="AWT-EventQueue-0", group="main")

17

TRACE represents a Java stack trace. Each trace consists
of a series of stack frames. Other records refer to
TRACEs to identify (1) where object allocations have
taken place, (2) the frames in which GC roots were
found, and (3) frequently executed methods.

TRACE 306106:
! java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:Unknown line)
! java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:Unknown line)
TRACE 306095:
! java.lang.Object.wait(Object.java:Unknown line)
! java.lang.ref.Reference$ReferenceHandler.run(Reference.java:Unknown line)
TRACE 317114:
! sun.java2d.Disposer.run(Disposer.java:Unknown line)
! java.lang.Thread.run(Thread.java:Unknown line)

18

HEAP DUMP is a complete snapshot of all live objects in the Java
heap. Following distinctions are made:

ROOT root set as determined by GC
CLS classes
OBJ instances
ARR arrays

OBJ 50036a24 (sz=392, trace=306854, class=javax.swing.JLabel@50000868)
OBJ 50036a27 (sz=24, trace=300098, class=java.util.ArrayList@5000005b)
OBJ 50036a29 (sz=16, trace=306857, class=javax.swing.event.EventListenerList@50002745)
OBJ 50036a2a (sz=24, trace=306356, class=java.lang.ref.WeakReference@50000037)

19

SITES is a sorted list of allocation sites. This identiﬁes
the most heavily allocated object types, and the TRACE
at which those allocations occurred.

SITES BEGIN (ordered by live bytes) Wed May 27 07:34:16 2009
percent live alloc'ed stack class
rank self accum bytes objs bytes objs trace name
1 9,88% 9,88% 2486200 3 2486200 3 317684 int[]
2 2,13% 12,01% 535440 6693 535760 6697 310354 javax.swing.text.html.InlineView
3 2,07% 14,08% 521592 159 623912 168 306967 char[]
4 1,78% 15,86% 447696 18654 450672 18778 305960 java.awt.Rectangle
5 1,72% 17,58% 432240 18010 599808 24992 310036 java.util.Hashtable$Entry
6 1,69% 19,27% 426240 3330 426368 3331 309154 javax.swing.text.html.ParagraphView

20

NetBeans Profiler

“
The NetBeans profiler provides expert
assistance for optimizing your application's
speed and memory usage, and makes it
easier to build reliable and scalable Java SE,
JavaFX and Java EE applications.

http://www.netbeans.org/features/java/profiler.html 21

WebApp

Inicializa a
aplicação web em
modo de proﬁling

22

Qual método gastou mais
tempo de processamento
durante a bateria de
testes?

23

Memória
vs
Garbage Collector

24

Memória disponível
x
Memória em uso

25

Threads alocadas
x
Classes carregadas

26

Quais objetos
ocuparam mais
memória?

27

Threads alocadas

28

Acabou a memória
disponível.

29

Mesmo erro no log
do Tomcat do
NetBeans

30

The Eclipse

Test & Performance
Tools Platform
(TPTP)

The Eclipse Test and Performance Tools Platform
(TPTP) Project provides an open platform
supplying powerful frameworks and services that
allow software developers to build unique test and
performance tools, both open source and
commercial, that can be easily integrated with the
platform and with other tools.

http://www.eclipse.org/tptp/ 31

instalação do plugin via
software update

33

atenção ao
servidor

TPTP

34

pacotes que
serão instalados

35

última
checagem...

36

...
38

http://www.eclipse.org/tptp/
home/downloads/4.5.0/
documents/quicktour/
WTP_viewlet20061206/
WTP_viewlet20061206.swf

40

Usando HPROF, NetBeans ou Eclipse,
realizar o proﬁling da alguma aplicação web Java
durante uma sessão de testes de carga. 41

JProfiler

“ JProfiler's intuitive GUI helps you find
performance bottlenecks, pin
down memory leaks and resolve
threading issues.

http://www.ej-technologies.com/products/jprofiler/overview.html 42

1 desenvolvedor

N desenvolvedores

43

Tempo de execução de
cada método

44

Número de
instâncias de cada
classe

45

Grafo de
referências entre
objetos
46

Invocação entre
métodos

47

Memória consumida
por cada método

48

Threads do
servidor

49

Quais threads estão
sendo bloqueadas e por
quê.

50

JBoss Profiler

“ JBoss Profiler is a log based profiler using
JVMPI and JVMTI. It uses an agent written in C
that captures events from the JVM and logs to
disk. A web application running on JBoss or
another machine can be used to analyze these
logs through a web browser.

http://www.jboss.org/jbossprofiler/ 52

JBoss Proﬁler
instalação

unzip jboss-profiler-2.0.Beta3.SP1.zip

53

JBoss Proﬁler
instalação

• Copiar para JBOSS_HOME/bin
• jboss-profiler.jar,
• jboss-profiler.properties,
• jboss-profiler-plugins.jar

• Copiar para JBOSS_HOME/server/<conf>/deploy
• jboss-profiler.sar

• Se JBoss 4.2x, copie para JBOSS_HOME/bin:
• javassist.jar
54

JBoss Proﬁler
instalação

• Em JBOSS_HOME/bin/jboss-profiler.properties

# Pacote a ser monitorado pelo Profiler
includes=br.com.seatecnologia.jbosstuning.*

• Em JBOSS_HOME/bin/run.conf

# Ativacao do JBoss Profiler
JAVA_OPTS="$JAVA_OPTS
-javaagent:jboss-profiler.jar
-Djboss-profiler.properties=jboss-profiler.properties"

55

JBoss Proﬁler
instalação

Reinicialize o JBoss

Ctrl+C

56

JBoss Proﬁler
utilização

• Inicie o JBoss Profiler
java -jar jboss-profiler-client.jar startProfiler

• Execute a aplicação
Hora de executar o plano de teste do JMeter

• Pare o JBoss Profiler
java -jar jboss-profiler-client.jar stopProfiler

• Colete os dados para análise
java -jar jboss-profiler-client.jar getSnapshot 1

57

java -jar jboss-profiler-client.jar getSnapshot 1

Diretório criado

Arquivos com os
resultados do proﬁling

Diretório de instalação
do jboss-proﬁler

58

Duração do teste

Thread mais demorada Métodos mais
demorados

Métodos que mais
usaram a CPU

59

Nova interface Web do
JBossProﬁler2

60

MBeans do
JBoss Proﬁler
(jboss-proﬁler.sar)

61

Operações do JBoss
Proﬁler via MBean

62

Twiddle:
--------
Information:
./twiddle.sh get 'org.jboss.profiler:service=Profiler' Running
./twiddle.sh get 'org.jboss.profiler:service=Profiler' Enabled
./twiddle.sh get 'org.jboss.profiler:service=Profiler' Memory
./twiddle.sh get 'org.jboss.profiler:service=Profiler' File
./twiddle.sh get 'org.jboss.profiler:service=Profiler' EJB
./twiddle.sh get 'org.jboss.profiler:service=Profiler' Servlet
./twiddle.sh get 'org.jboss.profiler:service=Profiler' JSF
./twiddle.sh get 'org.jboss.profiler:service=Profiler' JMX
./twiddle.sh get 'org.jboss.profiler:service=Profiler' RMI
./twiddle.sh get 'org.jboss.profiler:service=Profiler' CORBA

Operations:
./twiddle.sh invoke 'org.jboss.profiler:service=Profiler' startProfiler
./twiddle.sh invoke 'org.jboss.profiler:service=Profiler' stopProfiler
./twiddle.sh invoke 'org.jboss.profiler:service=Profiler' enableProfiler
./twiddle.sh invoke 'org.jboss.profiler:service=Profiler' disableProfiler
./twiddle.sh invoke 'org.jboss.profiler:service=Profiler' clearSnapshots
./twiddle.sh invoke 'org.jboss.profiler:service=Profiler' addClasses org.jboss.test.* public
./twiddle.sh invoke 'org.jboss.profiler:service=Profiler' removeClasses org.jboss.test.*
./twiddle.sh invoke 'org.jboss.profiler:service=Profiler' listClasses

63

YourKit

“ With YourKit solutions, both CPU and
memory proﬁling have come to the highest
professional level, where one can proﬁle even
huge applications with maximum productivity and
zero overhead.

http://www.yourkit.com/ 64

Informe a licença que foi
enviada por email.

67

Tela de
conﬁguração
68

Nenhum aplicativo
para proﬁling

Conectar a JEE
Server Local

69

Escolha o
servidor a ser
monitorado
70

Conﬁgurações
especíﬁcas do
servidor escolhido
71

Script de
inicialização do
servidor gerado
pelo YourKit

72

JBoss
automaticamente
identiﬁcado

http://www.yourkit.com/docs/80/help/ 73

Primeira tela do
proﬁler

74

Após iniciar o
proﬁling de
CPU...
...estatísticas de
execução são
apresentadas.

75

Ao ﬁnal dos testes, salve os
dados coletados para análise
mais detalhada.

76

Métodos invocados
por cada thread

78

Métodos que mais
consumiram CPU

79

Lista de todos os
métodos executados
durante os testes

80

Análise de JSPs e
Servlets

81

Uso da memória

82

Como o GC se
comportou.

83

Habilitar
telemetria de
threads

84

Threads do
conector HTTP

85

Captura dados da
memória para
análise ﬁna.

86

Abra o snapshot
criado

87

Dicas para otimização
da memória

89

Em todas as telas há links
diretos para a documentação
da ferramenta

90

Já sabem o
que fazer, né?
;-)

91

Java Profiling Tools

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Destaque

Destaque (19)

Semelhante a Java Profiling Tools

Semelhante a Java Profiling Tools (20)

Mais de SEA Tecnologia

Mais de SEA Tecnologia (20)

Último

Último (20)

Java Profiling Tools