ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzam4_5.4.0.1/rzam4hpofsdirstructperf.htm

55 lines
3.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="Directory structure and performance (HPOFS)" />
<meta name="abstract" content="HPOFS volumes have a dual directory structure to access files. Both a hash and hierarchical structure exist to provide a primary and secondary path to the file data. If the primary directory structure becomes damaged, the secondary path is used." />
<meta name="description" content="HPOFS volumes have a dual directory structure to access files. Both a hash and hierarchical structure exist to provide a primary and secondary path to the file data. If the primary directory structure becomes damaged, the secondary path is used." />
<meta name="DC.Relation" scheme="URI" content="rzam4highperfofs.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzam4hpofsdirstructperf" />
<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>Directory structure and performance (HPOFS)</title>
</head>
<body id="rzam4hpofsdirstructperf"><a name="rzam4hpofsdirstructperf"><!-- --></a>
<img src="./delta.gif" alt="Start of change" /><!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Directory structure and performance (HPOFS)</h1>
<div><p>HPOFS volumes have a dual directory structure to access files.
Both a hash and hierarchical structure exist to provide a primary and secondary
path to the file data. If the primary directory structure becomes damaged,
the secondary path is used.</p>
<p>The hash directory structure is designed to reduce the amount of media
I/O required, which improves performance for file access. Because of this
hash directory structure, directory depth has less effect on performance than
if the directory were searched hierarchically. For example, if /DIRECTORY1
contains 1000 files and /DIRECTORY2 contains 100 files, file search times
for files in /DIRECTORY1 will generally take no longer than file searches
in /DIRECTORY2. This is because the system performs the searches by using
the hash structure, not the hierarchical structure. </p>
<p>Directory depth has less effect on performance for a hash search than for
a hierarchical search. However, the overall directory depths and total number
of files on a volume will effect performance. In general, a volume with fewer
files on it will result in better file performance than a volume with more
files.</p>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzam4highperfofs.htm" title="High performance optical file system (HPOFS) is an IBM-developed media format architecture available to use when initializing optical media on the i5/OS.">High Performance Optical File System</a></div>
</div>
</div>
<img src="./deltaend.gif" alt="End of change" /></body>
</html>