ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzahx_5.4.0.1/rzahxplanbench.htm

80 lines
5.9 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="Set system benchmarks" />
<meta name="abstract" content="Setting good system benchmarks will give you performance data for a properly tuned system. These performance benchmarks from both before and after system changes provide important information for both troubleshooting and planning." />
<meta name="description" content="Setting good system benchmarks will give you performance data for a properly tuned system. These performance benchmarks from both before and after system changes provide important information for both troubleshooting and planning." />
<meta name="DC.Relation" scheme="URI" content="rzahxplanparent.htm" />
<meta name="DC.Relation" scheme="URI" content="rzahxcollectdatacs.htm" />
<meta name="DC.Relation" scheme="URI" content="rzahxpexparent.htm" />
<meta name="DC.Relation" scheme="URI" content="http://www.ibm.com/servers/eserver/iseries/hardware/threeinone" />
<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="rzahxplanbench" />
<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>Set system benchmarks</title>
</head>
<body id="rzahxplanbench"><a name="rzahxplanbench"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Set system benchmarks</h1>
<div><p>Setting good system benchmarks will give you performance data for
a properly tuned system. These performance benchmarks from both before and
after system changes provide important information for both troubleshooting
and planning.</p>
<p>You should establish system benchmarks before any major change in the system
configuration, for example adding a new interactive application or performing
a system upgrade. Maintaining accurate benchmark information can provide essential
troubleshooting information. At a minimum, benchmarks should include current
collection objects from Collection Services. Depending on your environment
you may need to maintain more detailed information using Performance Explorer.</p>
<p>Setting up a benchmark requires:</p>
<ul><li>That the correct <span class="keyword">iSeries™</span> configuration
is available</li>
<li>That the application and the data are representative and valid</li>
<li>That the correct version of all programs and software to be used are available</li>
<li>That the required number of users and workstations are available to run
the test</li>
<li>That the transactions are well defined for each user</li>
</ul>
<p>Running meaningful benchmarks for interactive workloads is almost impossible
without special equipment that allows you to simulate a user at a workstation.
To run a batch benchmark is, of course, not as complex a task as to test performance
of interactive applications, and the first three points above are still valid
for this type of test. However, setting system benchmarks on concurrent batch
and interactive work, which is frequently the actual customer environment,
also requires the appropriate number of users and workstations.</p>
<p>IBM<sup>®</sup> developed
a benchmark called the Three-in-One Benchmark to mirror the real-world demands
facing IT companies. The Three-In-One Benchmark clearly demonstrates that
the <span class="keyword">iSeries</span> server is an excellent
solution for today's small and medium businesses, which helps them run the
applications they need without worrying about performance.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahxplanparent.htm" title="Setting performance objectives for your iSeries server will allow you to have measurable performance benchmarks to compare your performance data. This topic will explain how to set those benchmarks and how to use them later.">Plan for performance</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><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="relinfo"><strong>Related information</strong><br />
<div><a href="http://www.ibm.com/servers/eserver/iseries/hardware/threeinone" target="_blank">Three-In-One Benchmark</a></div>
</div>
</div>
</body>
</html>