Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

nfs4_max_transfer_size(5) [hpux man page]

nfs4_max_transfer_size(5)					File Formats Manual					 nfs4_max_transfer_size(5)

NAME

       nfs4_max_transfer_size - control the size of the data portion of a NFS version 4 read, write, readdir, or readdirplus request

VALUES

   Failsafe
   Default
   Allowed values
   Recommended values
       A warning will be issued at runtime if the tunable is set to a value greater than 1048576 since this is outside the tested limits.  This is
       not a serious warning but just an information message for the administrator.

DESCRIPTION

       controls the maximum size of the data portion of a NFS version 4 read, write, readdir, or readdirplus request. This parameter controls both
       the maximum size of a request that the server returns as well as the maximum size of a request that the client generates.

   Who Is Expected to Change This Tunable?
       Distributed file system administrators should examine this value if they want to decrease or increase the default size of a NFS packet.

   Restrictions on Changing
       The  tunable  is  dynamic; however, the transfer size for a file system is set when the file system is mounted. To affect a particular file
       system, unmount and mount the file system after changing this parameter.

       The actual NFS version 4 transfer size is controlled by these tunable parameters: and The actual transfer size will depend on  the  tunable
       with  the  smallest value. For NFS version 4 traffic increase and to the same value to increase the transfer size. To decrease the transfer
       size, just changing is sufficient.

   When Should the Value of This Tunable Be Raised?
       An increase in the transfer size will result in fewer requests to the NFS server at the expense of system resources on both the NFS  client
       and NFS server.

   What Are the Side Effects of Raising the Value?
       An increase in system resources on both the NFS client and NFS server.

   When Should the Value of This Tunable Be Lowered?
       In the event of NFS communication failures, the value should be changed back to the default value.

   What Are the Side Effects of Lowering the Value?
       An increase in NFS version 4 network traffic caused by an increase in the number of I/O requests.

WARNINGS

       All  HP-UX kernel tunable parameters are release specific.  This parameter may be removed or have its meaning changed in future releases of
       HP-UX.

       Installation of optional kernel software, from HP or other vendors, may cause changes to tunable  parameter  values.   After  installation,
       some  tunable  parameters may no longer be at the default or recommended values.  For information about the effects of installation on tun-
       able values, consult the documentation for the kernel software being installed.	For information about optional kernel  software  that  was
       factory installed on your system, see at

AUTHOR

       was developed by Sun Microsystems, Inc.

SEE ALSO

       kctune(1M), sam(1M), gettune(2), settune(2), nfs4_bsize(5), nfs4_max_transfer_size_cots(5), values(5).

							     Tunable Kernel Parameters					 nfs4_max_transfer_size(5)

Check Out this Related Man Page

nfs3_nra(5)							File Formats Manual						       nfs3_nra(5)

NAME

       nfs3_nra - control the number of read-ahead operations queued by the NFS version 3 client when sequentially accessing a file

VALUES

   Failsafe
   Default
   Allowed values
   Recommended values
       A  warning will be issued at runtime if the tunable is set to a value greater than 16 since this is beyond the tested limit.  This is not a
       serious warning but just an information message for the administrator.

DESCRIPTION

       controls the number of read-ahead operations that are queued by the NFS version 3 client when sequential access to a  file  is  discovered.
       These read-ahead operations increase concurrency and read throughput.  Each read-ahead request is generally for 32768 bytes of file data.

   Who Is Expected to Change This Tunable?
       The distributed file system administrator should examine this value depending on network bandwidth and memory pressure on the client.

   Restrictions on Changing
       The tunable is dynamic; tuning will take effect immediately on the running system.

   When Should the Value of This Tunable Be Raised?
       If  the network is very high bandwidth and the client and server have sufficient resources, increase this value to more effectively utilize
       the available network bandwidth, the client resources, and the server resources.

   What Are the Side Effects of Raising the Value?
       Tuning incorrectly based on network bandwidth can cause performance problems.

   When Should the Value of This Tunable Be Lowered?
       In a very low bandwidth network, decrease this value so the NFS client does not overload the network.

   What Are the Side Effects of Lowering the Value?
       Tuning incorrectly based on network bandwidth can cause performance problems.

WARNINGS

       All HP-UX kernel tunable parameters are release specific.  This parameter may be removed or have its meaning changed in future releases	of
       HP-UX.

       Installation  of  optional  kernel  software, from HP or other vendors, may cause changes to tunable parameter values.  After installation,
       some tunable parameters may no longer be at the default or recommended values.  For information about the effects of installation  on  tun-
       able  values,  consult  the documentation for the kernel software being installed.  For information about optional kernel software that was
       factory installed on your system, see at

AUTHOR

       was developed by Sun Microsystems, Inc.

SEE ALSO

       kctune(1M), sam(1M), gettune(2), settune(2), nfs2_nra(5), nfs4_nra(5), values(5).

							     Tunable Kernel Parameters						       nfs3_nra(5)
Man Page