HP-UX 11i Version 2 Installation and Update Guide, September 2004
Table Of Contents
- 1 Welcome to HP-UX 11i Version 2
- 2 System Requirements for Cold-Installing and Updating
- 3 Choosing an Installation Method
- Supported Cold-Install Paths to HP-UX 11i v2
- Supported Update Paths to HP-UX 11i v2
- Deciding Which Method to Use
- Time to Complete a Cold Install or Update
- When to Cold-Install
- When to Update
- Additional Cold-Install Considerations
- Additional Update Considerations
- Requirement for Updating from HP-UX 11i v1.6 (B.11.22)
- Requirement for Updating from Earlier Releases of HP-UX 11i v2 (B.11.23)
- HP Service Partition Is Not Created During Update (Itanium-based Systems Only)
- Update-UX Contains a Default-Installed Selection File
- Update-UX Creates Two Backup Configurations
- Security Considerations
- Standard HP-UX Bundle Considerations
- Online Diagnostics
- Offline Diagnostics
- The Next Step
- 4 Preparing to Install or Update to HP-UX 11i v2
- 5 Cold-Installing HP-UX 11i v2
- 6 Updating to HP-UX 11i v2
- 7 Installing HP Applications and Patches
- 8 Verifying System Install or Update
- A Data Collection Tables
- B Known Problems and Troubleshooting
- C Controlling Memory Utilization of VxFS 3.5 on HP-UX
- D Software Distribution Media
- HP-UX 11i v2 Core Software Bundles
- HP-UX 11i v2 Always-Installed Patch Bundles
- HP-UX 11i v2 Always-Installed Software Bundles
- HP-UX 11i v2 Always-Installed Network and Mass Storage Drivers
- HP-UX 11i v2 Default-Installed Software Bundles
- HP-UX 11i v2 Selectable Software Bundles
- HP-UX 11i v2 Selectable Network Drivers

Controlling Memory Utilization of VxFS 3.5 on HP-UX 11i v2
Controlling the inode Cache
Appendix C 169
Controlling the inode Cache
As a matter of course, VxFS file systems allocate and free up inodes as
required by the load on the file system. VxFS caches these inodes for
better performance (faster lookups). In general, larger inode caches help
file systems perform better for file server and web server loads. The
global (static) tunable vx_ninode represents the maximum possible size
of the VxFS inode cache.
Normally, the size of the inode cache is decided (auto-tuned) at boot time
by VxFS depending on the amount of physical memory in the machine,
provided that the value of vx_ninode is set to zero (default).
However, systems low on RAM (typically less than or equal to 1GB/CPU)
may not require a large inode cache if file systems are not exposed to file
server and web server loads, or when file system performance is not
critical. HP recommends that you set the value of vx_ninode to more
than that of
nfile
, an HP-UX tunable that represents the maximum
number of file descriptors.