On the NFS client, you run the following: nfsstat -c Also, it's very important to put the NFS server in the same subnet as the NFS client when designing the network. When the badcalls is greater than 0, than the underlying network needs to be checked, as there might be latency. The most important field to check is the badcalls, which represents the total number of calls rejected by the RPC layer. The output should be similar to the below: Server rpc stats: On the NFS server, run the following command: nfsstat -s The nfsstat command displays statistical information about the NFS and Remote Procedure Call (RPC) interfaces to the kernel. Understanding the output of the tools can help with optimizing NFS performance. The two most important tools I have used over the years to analyze the performance of NFS from both the server and client perspective are nfsstat and nsfiostat. The two tools are part of the nfs-utils package and its needs to be installed as such: yum install -y nfs-utils However, because NFS relies on the existing network infrastructure, any glitches on the network may affect the performance of the connection. It allows for fast, seamless sharing of files across a network. The network filesystem ( NFS) allows machines to mount a disk partition on a remote machine as if it were a local disk.
0 Comments
Leave a Reply. |