109 lines
8.0 KiB
HTML
109 lines
8.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="Performance explorer concepts" />
|
||
|
|
<meta name="abstract" content="Performance explorer works by collecting detailed information about a specified system process or resource. This topic explains how performance explorer works, and how best to use it." />
|
||
|
|
<meta name="description" content="Performance explorer works by collecting detailed information about a specified system process or resource. This topic explains how performance explorer works, and how best to use it." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxpexparent.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxpexconpexdef.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxpexcondbfiles.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxreportpex.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxcollectdatacs.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxpexcfg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxpexcfg.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzahxpexcon" />
|
||
|
|
<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>Performance explorer concepts</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzahxpexcon"><a name="rzahxpexcon"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Performance explorer concepts</h1>
|
||
|
|
<div><p>Performance explorer works by collecting detailed information about
|
||
|
|
a specified system process or resource. This topic explains how performance
|
||
|
|
explorer works, and how best to use it.</p>
|
||
|
|
<p>Performance explorer has advantages for people who need detailed performance
|
||
|
|
analysis on an <span class="keyword">iSeries™</span> server.
|
||
|
|
Using performance explorer you can:</p>
|
||
|
|
<ul><li>Determine what is causing a performance problem on the system down to
|
||
|
|
the level of user, job, file, object, thread, task, program, module, procedure,
|
||
|
|
statement, or instruction address.</li>
|
||
|
|
<li>Collect performance information on user-developed and system software.</li>
|
||
|
|
<li>Do a detailed analysis on one job without affecting the performance of
|
||
|
|
other operations on the system.</li>
|
||
|
|
<li> Analyze data on a system other than the one on which it was collected.
|
||
|
|
For example, if you collect data on a managed system in your network, you
|
||
|
|
can send it to the central site system for analysis.</li>
|
||
|
|
</ul>
|
||
|
|
<p>Like Collection Services, performance explorer collects data for later
|
||
|
|
analysis. However, they collect very different types of data. Collection Services
|
||
|
|
collects a broad range of system data at regularly schedules intervals, with
|
||
|
|
minimal system resource consumption. In contrast, performance explorer starts
|
||
|
|
a session that collects trace-level data. This trace generates a large amount
|
||
|
|
of detailed information about the resources consumed by an application, job,
|
||
|
|
or thread. Specifically, you can use Performance Explorer to answer specific
|
||
|
|
questions about areas like system-generated disk I/O, procedure calls, Java™ method
|
||
|
|
calls, page faults, and other trace events. It is the ability to collect very
|
||
|
|
specific and very detailed information that makes the performance explorer
|
||
|
|
effective in helping isolate performance problems. For example, Collection
|
||
|
|
Services can tell you that disk storage space is rapidly being consumed. You
|
||
|
|
can use performance explorer to identify what programs and objects are consuming
|
||
|
|
too much disk space, and why.</p>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />When performance explorer is running, it creates only the files
|
||
|
|
that are needed for the collection.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> You can collect performance explorer data and Collections Services data
|
||
|
|
at the same time.</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">How performance explorer works</h4><p>The following figure
|
||
|
|
should help you become familiar with the normal path through the performance
|
||
|
|
explorer. For details on each of these steps, see Configure performance explorer.
|
||
|
|
The figure shows a basic work cycle that consists of the following steps:</p>
|
||
|
|
<ol><li>Define a performance explorer data collection. You can also add a filter
|
||
|
|
to limit the amount of data collected by specifying a compare value for specific
|
||
|
|
events.</li>
|
||
|
|
<li>Start the performance explorer to collect the data based on your definition.</li>
|
||
|
|
<li>Run your program, command, or workload.</li>
|
||
|
|
<li>End the collection, which saves the collected data to a set of database
|
||
|
|
files.</li>
|
||
|
|
<li>Create and print reports from the database files.</li>
|
||
|
|
</ol>
|
||
|
|
<br /><img src="rzahx503.gif" alt="Performance explorer basic flow" /><br /><p>To learn more about performance explorer, refer to any of the following
|
||
|
|
performance explorer topics.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahxpexconpexdef.htm">Performance explorer definitions</a></strong><br />
|
||
|
|
The parameters and conditions that determine what data performance explorer collects and how it collects it are configured and stored using performance explorer definitions. This topic explains how to use these definitions and provides a sample illustrating a simple definition.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahxpexcondbfiles.htm">Performance explorer database files</a></strong><br />
|
||
|
|
The data that performance explorer collects is stored in performance explorer database files.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzahxreportpex.htm">Performance explorer reports</a></strong><br />
|
||
|
|
After you have collected performance data with a performance explorer session, you can view it by running the included reports or by querying the database files directly.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahxpexparent.htm" title="Collects more detailed information about a specific application, program or system resource, and provides detailed insight into a specific performance problem. This includes the capability both to perform several types and levels of traces and to run detailed reports.">Performance explorer</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzahxcollectdatacs.htm" title="Use Collection Services to collect performance data for later analysis by the Performance Tools for iSeries licensed program or other performance report applications, iSeries Navigator monitors, and the graph history function. (If you prefer viewing real-time performance data, system monitors provide an easy-to-use graphical interface for monitoring system performance.)">Collection Services</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzahxpexcfg.htm" title="To collect detailed trace information, you need to tailor performance explorer to work optimally with the application process from which the trace is being taken.">Configure performance explorer</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|