Veritas™ File System 5.0.1 Administrator's Guide

either the system memory size, which is the default, or the value of the tunable
if explicitly set, whichever is larger. Thus, dynamically increasing the tunable to
a value that is more than two times either the default value or the user-defined
value, if larger, may cause performance degradation unless the system is rebooted.
Decreasing the value of vx_ninode will not succeed if the doing so requires a
change to internal hash tables, in which case the change is marked for the next
boot automatically and will take effect on the subsequent boot. If the change to
the internal hash tables is not required, VxFS frees the cached objects so that the
total number of inodes in the cache is equal to or less than the specified vx_ninode
value.
Examples of changing the vx_inode tunable value
The following are examples of changing the vx_ninode tunable value.
Reporting the current value of vx_ninode
# kctune vx_ninode
This command displays the current value of vx_ninode.
Setting vx_ninode
# kctune -s vx_ninode=10000
This command sets vx_ninode to 10000, the specified value.
Restoring vx_ninode to its default value
# kctune -s vx_ninode=
This command restores vx_ninode to its default value by clearing the user-specified
value. The default value is the value determined by VxFS to be optimal based on
the amount of system memory, which is used if vx_ninode is not explicitly set.
Delaying a change to vx_ninode until after a reboot
# kctune -h -s vx_ninode=10000
If the -h option is specified, the specified value for vx_ninode does not take effect
until after a system reboot.
VxFS performance: creating, mounting, and tuning file systems
Tuning the VxFS file system
46