ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzahq_5.4.0.1/rzahqperfstgvsded.htm

70 lines
4.6 KiB
HTML
Raw Permalink Normal View History

2024-04-02 14:02:31 +00:00
<?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 xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="dc.language" scheme="rfc1766" 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. -->
<meta name="dc.date" scheme="iso8601" content="2005-09-13" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<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))' />
<title>iSeries storage spaces versus dedicated disks</title>
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
<link rel="stylesheet" type="text/css" href="ic.css" />
</head>
<body>
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
<img src="delta.gif" alt="Start of change" /><img src="delta.gif" alt="Start of change" />
<a name="rzahqperfstgvsded"></a>
<h3 id="rzahqperfstgvsded">iSeries storage spaces versus dedicated disks</h3>
<p>For performing processor or memory intensive work on an integrated server,
the performance characteristics are equivalent to a stand-alone server using
dedicated disk drives. Since the integrated server disk drives are allocated
out of iSeries&trade; storage, the disk performance is dependent on the iSeries.</p>
<p><span class="bold">Greater disk performance capacity with iSeries shared disks</span></p>
<p>On most stand-alone servers a few disks are dedicated to each server. For
applications with a small average disk load, the performance is adequate.
However, there can be periods of time where the server performance is limited
by the capacity of those few dedicated disks.</p>
<p>When the same group of servers is integrated with the iSeries, the virtual
disks are spread across more iSeries hard disks. The total average disk
load does not need to be any greater than for a group of servers with dedicated
disks. But, when an individual server temporarily needs more disk performance
capacity, it is available through the larger set of iSeries disks.</p>
<p>On servers with dedicated disks, the disk response times tend to be relatively
steady. For example, you might take advantage of the predictable response
time and configure the Windows Performance Monitor to produce alerts when
disk response times exceed typical thresholds and indicate exceptional conditions
which may need your attention.</p>
<p>On an integrated server, the iSeries storage, CPU and memory are shared
between the integrated server and iSeries applications. It is normal for Windows
disk response to swing through a larger range. Short periods might occur where
I/O operations from multiple integrated servers, or other iSeries operations
contend for the same disk. Some disk intensive iSeries applications (like SAV and RST), can
reduce the disk performance seen on the Windows server for a period of time.
This can make it more difficult to choose a threshold value for short time
periods.</p>
<p><span class="bold">Consider the entire group of disks when you evaluate storage
bottlenecks</span></p>
<p>The iSeries server storage space appears as one disk drive within Windows.
When the Physical Disk average queue length (in Windows Performance Monitor)
exceeds two, the server performance is not necessarily disk constrained. Assuming
that memory paging issues have been ruled out, a queue length of two or a
Windows disk utilization of 100% only points to a storage bottleneck if there
is only one physical disk drive to perform the operations. There are usually
multiple disks on the iSeries server in the storage space ASP operating in parallel.
Typically, two times the number of disks in the ASP might point toward a disk
bottleneck. You might also need to account for the average queue lengths of
all the servers using the storage ASP.</p><img src="deltaend.gif" alt="End of change" /><img src="deltaend.gif" alt="End of change" />
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
</body>
</html>