87 lines
7.0 KiB
HTML
87 lines
7.0 KiB
HTML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!DOCTYPE html
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html lang="en-us" xml:lang="en-us">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<meta name="security" content="public" />
|
|
<meta name="Robots" content="index,follow" />
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
|
<meta name="DC.Type" content="concept" />
|
|
<meta name="DC.Title" content="Java profiling performance tools" />
|
|
<meta name="abstract" content="System wide central processing unit (CPU) profiling calculates the relative amount of CPU time that is spent in each Java method and all system functions in use by your Java program." />
|
|
<meta name="description" content="System wide central processing unit (CPU) profiling calculates the relative amount of CPU time that is spent in each Java method and all system functions in use by your Java program." />
|
|
<meta name="DC.Relation" scheme="URI" content="pdc.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="tuning.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="evenperf.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="runtperf.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="gc.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="jnmiperf.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="jmiperf.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="excperf.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="callperf.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="colpdc.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="jvmpi.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="profperf" />
|
|
<meta name="DC.Language" content="en-us" />
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
|
<!-- US Government Users Restricted Rights -->
|
|
<!-- Use, duplication or disclosure restricted by -->
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
|
<title>Java profiling performance tools</title>
|
|
</head>
|
|
<body id="profperf"><a name="profperf"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">Java profiling performance tools</h1>
|
|
<div><p>System wide central processing unit (CPU) profiling calculates
|
|
the relative amount of CPU time that is spent in each Java™ method
|
|
and all system functions in use by your Java program.</p>
|
|
<p>Use a Performance Explorer (PEX) definition that traces performance monitor
|
|
counter overflow (*PMCO) run cycle events. Samples are typically specified
|
|
in intervals of one millisecond. To collect a valid trace profile, you should
|
|
run your Java application until it accumulates two to three minutes
|
|
of CPU time. This should produce over 100,000 samples. The Print Performance
|
|
Explorer Report (PRTPEXRPT) command produces a histogram of CPU time that
|
|
is spent across the entire application. This includes every Java method
|
|
and all system-level activity. The <a href="pdc.htm">Performance Data
|
|
Collector (PDC) tool</a> also provides profile information about the programs
|
|
that run on the iSeries™ server.</p>
|
|
<div class="note"><span class="notetitle">Note:</span> CPU profiling does not show relative CPU usage for Java programs
|
|
that are interpreted.</div>
|
|
</div>
|
|
<div>
|
|
<ul class="ullinks">
|
|
<li class="ulchildlink"><strong><a href="jvmpi.htm">Java Virtual Machine Profiler Interface</a></strong><br />
|
|
The Java Virtual Machine Profiler Interface (JVMPI) is an
|
|
experimental interface for profiling the Java virtual machine (JVM), which was first
|
|
disclosed and implemented in Sun's Java 2 SDK, Standard Edition (J2SDK), version
|
|
1.2.</li>
|
|
</ul>
|
|
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="tuning.htm" title="You should take several aspects of Java application performance into consideration when building a Java application for your iSeries server.">Tune Java program performance with IBM Developer Kit for Java</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="evenperf.htm" title="The iSeries Java virtual machine enables the trace of certain Java events.">Java event trace performance tools</a></div>
|
|
<div><a href="runtperf.htm" title="Understanding the following considerations can help you improve the performance of your Java applications.">Java performance considerations</a></div>
|
|
<div><a href="gc.htm" title="Garbage collection is the process of freeing storage that is used by objects that are no longer referred to by a program. With garbage collection, programmers no longer have to write error prone code to explicitly "free" or "delete" their objects. This code frequently results in "memory leak" program errors. The garbage collector automatically detects an object or group of objects that the user program can no longer reach. It does this because there are no references to that object in any program structure. Once the object has been collected, you can allocate the space for other uses.">Java garbage collection</a></div>
|
|
<div><a href="jnmiperf.htm" title="Native method invocation on an iSeries server may not perform as well as native method invocation on other platforms.">Java Native Method Invocation performance considerations</a></div>
|
|
<div><a href="jmiperf.htm" title="Method inlining can significantly improve method call performance. Any method that is final is a potential candidate for inlining.">Java method inlining performance considerations</a></div>
|
|
<div><a href="excperf.htm" title="The iSeries exception architecture allows versatile interrupt and retry capabilities. It also allows mixed language interaction. Throwing Java exceptions on an iSeries server may be more expensive than on other platforms. This should not affect overall application performance unless Java exceptions are routinely used in the normal application path.">Java exception performance considerations</a></div>
|
|
<div><a href="callperf.htm" title="Java method call traces provide significant performance information about the time that is spent in each Java method.">Java call trace performance tools</a></div>
|
|
</div>
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
|
<div><a href="colpdc.htm" title="To collect Java performance data on an iSeries server, follow these steps.">Collect Java performance data</a></div>
|
|
</div>
|
|
|
|
<div class="linklist"><strong>Collected links</strong><br />
|
|
|
|
<div><a href="pdc.htm" title="The Performance Data Collector (PDC) tool provides profile information about the programs that run on the iSeries server.">Performance Data Collector (PDC) tool</a></div></div>
|
|
</div>
|
|
</body>
|
|
</html> |