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
Introduction
Appendix C168
Introduction
VxFS 3.5 caches objects in memory to improve performance. Most of the
memory consumed by VxFS is used to cache inodes (in the inode cache)
and metadata (in the buffer cache). The sizes of these caches and the
behavior of VxFS are controlled by a set of tunables. You can tailor the
performance of VxFS to meet a variety of usage scenarios while taking
into account variations in machine configurations via the use of these
tunables.
The default settings of these tunables are meant to provide good
performance for typical deployment configurations. However, these
default values can result in the VxFS driver consuming more memory,
especially when the file systems are under heavy file system load. For
machines low on RAM, these tunables may need to be manually turned
down depending on the expected use of the machine and the performance
required of the file system.
VxFS 3.5 exposes two global tunables, vx_ninode and vxfs_bc_bufhwm,
that control the size of the inode cache and buffer cache, respectively, and
thereby affect system memory consumption by the file system driver.
This appendix discusses when and why the sizes of the inode and buffer
caches need to be tuned down from their default values in certain
configurations. The following sections describe these tunables in detail
as well as the effects of changing their default values.