82 lines
5.2 KiB
HTML
82 lines
5.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 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>iSCSI attached server performance</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="rzahqiscsiattachedperf"></a>
|
||
|
|
<h3 id="rzahqiscsiattachedperf">iSCSI attached server performance</h3>
|
||
|
|
<p>For iSCSI attached servers, there are multiple configuration options to
|
||
|
|
adjust for better performance capacity as needed. Some options may require
|
||
|
|
different target disk configurations or volumes on the integrated servers.</p>
|
||
|
|
<p><span class="bold">Windows disk configuration</span></p>
|
||
|
|
<p>For iSCSI attached integrated servers, the virtual disk drives are optimized
|
||
|
|
for:</p>
|
||
|
|
<ul>
|
||
|
|
<li>1 disk partition per virtual drive.</li>
|
||
|
|
<li>1 gigabyte or larger storage spaces.</li>
|
||
|
|
<li>NTFS file system formatted with 4 kilobyte or larger cluster sizes.</li></ul>
|
||
|
|
<p>These guidelines allow the iSeries™ to efficiently manage the storage space
|
||
|
|
memory, improving the disk performance. These guidelines also affect IXS and
|
||
|
|
IXA attached servers, but to a much smaller degree.</p>
|
||
|
|
<p><img src="delta.gif" alt="Start of change" />If you use the Change Network Storage Space (CHGNWSSTG) CL
|
||
|
|
command to increase a storage space size, be sure to use the Windows Server
|
||
|
|
2003 DISKPART command to also increase the size of the partition on Windows.
|
||
|
|
</p>
|
||
|
|
<a name="wq14"></a>
|
||
|
|
<div class="notetitle" id="wq14">Note:</div>
|
||
|
|
<div class="notebody">For better performance, add a storage space to the server
|
||
|
|
instead of adding another disk partition in the new space.</div><img src="deltaend.gif" alt="End of change" />
|
||
|
|
<p><span class="bold">iSeries memory pools</span></p>
|
||
|
|
<p>For iSCSI attached servers, the storage operations occur through an iSeries memory pool. This memory essentially acts as a cache to the disk operations,
|
||
|
|
so the size of the memory can affect the Windows disk performance. This I/O
|
||
|
|
does not directly cause page faulting in the base pool. However, since pool
|
||
|
|
memory is shared with other i5/OS™ applications, Windows disk operations
|
||
|
|
may cause page faulting in other applications, or other applications may induce
|
||
|
|
paging of iSCSI disk operations. In extreme cases, you may need to adjust
|
||
|
|
memory pool sizes or assign applications to other memory pools to mitigate
|
||
|
|
memory problems.</p>
|
||
|
|
<p>IXS and IXA attached servers do not perform disk operations through a base
|
||
|
|
memory pool. They use reserved memory within the machine pool (System Pool
|
||
|
|
ID 1). Thus, the disk operations do not share memory with other applications.</p>
|
||
|
|
<p><span class="bold">iSCSI performance configurations</span></p>
|
||
|
|
<p>On iSCSI attached integrated servers, if a single network fabric is reaching
|
||
|
|
capacity, you can add channels with additional iSCSI HBAs in both the xSeries® and iSeries servers (assuming the interconnecting network also
|
||
|
|
has available bandwidth).</p>
|
||
|
|
<p>There are several ways that you can spread the iSCSI and network traffic
|
||
|
|
between the separate channels:</p>
|
||
|
|
<ul>
|
||
|
|
<li>Dedicate SCSI operations to one channel, and virtual Ethernet operations
|
||
|
|
to another.</li>
|
||
|
|
<li>Use two storage targets. Each target should be linked to a separate HBA
|
||
|
|
paths. See <a href="rzahqmanageiscsihostadapters.htm#rzahqmanageiscsihostadapters">Manage iSCSI host bus adapters</a>.
|
||
|
|
<ul>
|
||
|
|
<li>On Windows, direct applications to use both drives (if possible), or dedicate
|
||
|
|
the drives to different applications to spread the total disk operations between
|
||
|
|
the drives.</li>
|
||
|
|
<li>Configure the two disks in a Windows dynamic volume set with the data
|
||
|
|
striped across the two drives. As applications use the volume, the disk operations
|
||
|
|
will automatically balance across the drives in the volume set.</li></ul></li></ul><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>
|