[root@lab0-v3 ~]# mount -t nfs -o tcp,nfsvers=3 localhost:/images /mnt
[root@lab0-v3 ~]# cd /mnt
[root@lab0-v3 mnt]# time bash -c 'tar xf /root/linux-3.3.tar ; sync ;
rm -rf linux-3.3'
real2m26.698s
user0m0.334s
sys 0m6.943s
On Wed, Mar 21, 2012 at 6:22 AM, David Coulson
Weird - Actually slower than fuse. Does the 'nolock' nfs mount option
make a difference?
On 3/21/12 1:22 PM, Bryan Whitehead wrote:
[root@lab0-v3 ~]# mount -t nfs -o tcp,nfsvers=3 localhost:/images /mnt
[root@lab0-v3 ~]# cd /mnt
[root@lab0-v3 mnt]# time bash -c 'tar xf /root/linux-3.3.tar ;
[root@lab0-v3 ~]# mount -t nfs -o tcp,nfsvers=3,nolock localhost:/images /mnt
[root@lab0-v3 ~]# cd /mnt
[root@lab0-v3 mnt]# time bash -c 'tar xf /root/linux-3.3.tar ; sync ;
rm -rf linux-3.3'
real2m26.758s
user0m0.353s
sys 0m7.101s
[root@lab0-v3 mnt]#
On Wed, Mar 21, 2012 at 10:27
Bryan Whitehead dri...@megahappy.net writes:
I didn't see any sync's after the tar/rm commands...
By default, ext4 flushes both metadata and data every five seconds, so a
post-benchmark sync tends to make little difference on a reasonable large test,
but for completeness:
# time bash -c 'tar
