Terry Barnaby <terry1 <at> beam.ltd.uk> writes: > ... > # Test1, defaults: nfs version 4, sync > Server /etc/exports: "/data *.kingnet(rw)" > Client /etc/fstab: "king.kingnet:/data /data nfs defaults 0 0" > > dd if=/tmp/data.bin of=/data/tmp/data.bin bs=102400 > 32.9 MB/s > > dd if=/data/tmp/data.bin of=/tmp/data1.bin bs=102400 > 66.5 MB/s <+++++++++++++++++++++++++++++++++++++++++++++++++++ > > time tar -xf /tmp/jpgraph-3.5.0b1.tar > real 9m35.235s <=========================================== > > time cp -a /tmp/jpgraph-3.5.0b1 /data/tmp > real 6m6.373s > > # Test4, nfs version 3, sync > Server /etc/exports: "/data *.kingnet(rw,async)" > Client /etc/fstab: "king.kingnet:/data /data nfs defaults,nfsvers=3 0 0" > > dd if=/tmp/data.bin of=/data/tmp/data.bin bs=102400 > 34.6 MB/s > > dd if=/data/tmp/data.bin of=/tmp/data1.bin bs=102400 > 120 MB/s <+++++++++++++++++++++++++++++++++++++++++++++++++++ > > time tar -xf /tmp/jpgraph-3.5.0b1.tar > real 4m20.355s <=========================================== > > time cp -a /tmp/jpgraph-3.5.0b1 /data/tmp > real 6m8.394s > ... The results marked (<===, <+++) show a regression for NFS v4 vice NFS v3, a decline of 100% for each test case. I think you should let them know (BZ report) - the type of test performed would be of interest to them. I would suggest this as well: to test by eliminating a possible problem with network, you could perform NFS tests (as above) locally (on your client machine in question), that is, install NFS server and client software locally, export some dir locally, and mount the exported dir locally. That is, you would mostly test the NFS software only. JB -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
