Nfs optimization configuration test tutorial

(1), rsize and wsize optimization parameters test 1) normal mount test nfs write test [root@client ~]# mount -t nfs 192.168.0.107:/data /data/[root@client ~]# time Dd if=/dev/zero of=/data/testfile bs=16k count=16484real 0m9.347suser 0m0.002ssys 0m2.657snfs read test [root@client ~]# time dd if=/data/testfile of=/dev/Null bs=16kreal 0m11.674suser 0m0.003ssys 0m0.333s Tip: Test N times of reading and writing, look at the average of N times, use a multiple of 1024 [root@client ~]# rm -f /data/testfile [ ,null,null,3],Root@client ~]# umount /data/(2), plus rsize and wsize and noatime and nodiratime parameters test [root@client ~]# mount -t nfs -o rsize=32768,wsize=32768,noatime 192.168.0.107: /data /data/[root@client ~]# time dd if=/dev/zero of=/data/testfile bs=16k count=16484real 0m9.654suser 0m0.004ssys 0m0.485s[root@client ~]# time dd If=/data/testfile of=/dev/null bs=16kreal 0m10.850suser 0m0.001ssys 0m0.288s Description: The test results seem to have little effect, the environment is a virtual machine test environment, the effect may not be obvious, the production environment is still Many tests (3), client mount optimization [root@client ~]# mount -t nfs -o noatime, nodiratime 192.168.0.107:/data /data[root@client ~]# mount…skip…192.168.0.107:/data On /mnt type nfs (rw, noatime, nodiratime, addr=192.168.0.107) Description: noatime and nodiratime parameters, do not update the atime access time of files and directories when the file or directory is accessed, in the case of high concurrency, it is more effective < Br>