On 09/25/2011 04:39 PM, JB wrote: > Terry Barnaby<terry1<at> beam.ltd.uk> writes: > >> ... > > It would be useful to publish a test for > # Test4, defaults: nfs version 3 > that is with "sync" option, so we could see if similar degradation was > present with older protocol ? > > One other thing: it would be interesting to see the results if instead of > in-place (/data/...) execution of > time tar -xf ... > > you first untared your files into non-NFS dir > mkdir -p /tmp/untared > cd /tmp/untared > tar -xf /tmp/jpgraph-3.5.0b1.tar > > and then executed > 'time cp /tmp/untared/* /data/tmp/' > > JB > > Thanks for the reply. The extra test data is:
# 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 Basically NFS with sync for NFS version 3 and 4 is very slow, NFSV4 seems slowest. Note that CPU usage on both client and server is virtually nill during the tests (server waiting is for I/O 48% on dual core system). The server has 2 x SATA disks in RAID-1 for /data. I wonder if NFS is doing a complete sync() to disk on each file close ?? Cheers Terry -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
