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 Buffer Cache
Appendix C170
Controlling the Buffer Cache
VxFS 3.5 implements a private buffer cache used exclusively for
metadata. The allocations made for this buffer cache are not static but
grow and shrink during system usage, depending on the load on the file
system. The global (static) tunable vxfs_bc_bufhwm represents the
maximum possible size of the VxFS buffer cache.
The maximum size of the metadata buffer cache is set (auto-tuned) at
boot time based on system memory size, provided that the value of
vxfs_bc_bufhwm is set to zero (default).
Like with the tunable vx_ninode, a large metadata buffer cache can help
improve file system performance, especially during metadata-intensive
loads (stat, create, remove, link, lookup operations).
Systems low on RAM (having typically 1GB/CPU or less) may not need a
large metadata buffer cache if the file system load is not
metadata-intensive or when performance is not critical. In such
circumstances, the value of vxfs_bc_bufhwm can be manually tuned
down, subject to a minimum of 6MB.