65 lines
4.2 KiB
HTML
65 lines
4.2 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="Identify performance problem" />
|
||
|
|
<meta name="abstract" content="Learn the common steps involved with identifying a performance problem." />
|
||
|
|
<meta name="description" content="Learn the common steps involved with identifying a performance problem." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahxresearchparent.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="rzahxresearchidprob" />
|
||
|
|
<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>Identify performance problem</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzahxresearchidprob"><a name="rzahxresearchidprob"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Identify performance problem</h1>
|
||
|
|
<div><p>Learn the common steps involved with identifying a performance
|
||
|
|
problem.</p>
|
||
|
|
<p>When trying to identify a performance problem, it is important to assess
|
||
|
|
whether the hardware configuration is adequate to support the workload. Is
|
||
|
|
there enough CPU capacity? Is the main storage sufficient for the different
|
||
|
|
types of applications? Answering these questions first, perhaps through capacity
|
||
|
|
modeling techniques, prevents needless effort later.</p>
|
||
|
|
<p>With an understanding of the symptoms of the problem and the objectives
|
||
|
|
to be met, the analyst can formulate a hypothesis that may explain the cause
|
||
|
|
of the problem. The analyst can use commands and tools available with <span class="keyword">i5/OS™</span> and the Performance Tools
|
||
|
|
licensed program to measure the system performance.</p>
|
||
|
|
<p>Reviewing the measured data helps to further define the problem and helps
|
||
|
|
to validate or reject the hypothesis. Once the apparent cause or causes have
|
||
|
|
been isolated, a solution can be proposed. When you handle one solution at
|
||
|
|
a time, you can redesign and test programs. Again, the analyst's tools can,
|
||
|
|
in many cases, measure the effectiveness of the solution and look for possible
|
||
|
|
side effects.</p>
|
||
|
|
<p>To achieve optimum performance, you must recognize the interrelationship
|
||
|
|
among the critical system resources and attempt to balance these resources,
|
||
|
|
namely CPU, disk, main storage, and for communications, remote lines. Each
|
||
|
|
of these resources can cause a performance degradation.</p>
|
||
|
|
<p>Improvements to system performance, whether to interactive throughput,
|
||
|
|
interactive response time, batch throughput, or some combination of these,
|
||
|
|
may take many forms, from simply adjusting activity level or pool size to
|
||
|
|
changing the application code itself. In this instance, an activity level
|
||
|
|
is a characteristic of a subsystem that specifies the maximum number of jobs
|
||
|
|
that can compete at the same time for the processing unit.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahxresearchparent.htm" title="There are many options available to help you identify and resolve performance problems. Learn how to use the available tools and reports that can help you find the source of the performance problem.">Research a performance problem</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|