Re: how to set the default read/write block size for all transactions for optimal performance (e.g. anything similar to rsize, wsize nfs options?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



If you got some spare time, can you also benchmark this version..
http://ftp.zresearch.com/pub/gluster/glusterfs/1.4-qa/glusterfs-1.4.0qa29.tar.gz

--
Anand Babu Periasamy
GPG Key ID: 0x62E15A31
Blog [http://ab.freeshell.org]
The GNU Operating System [http://www.gnu.org]
Z RESEARCH Inc [http://www.zresearch.com]



Sabuj Pattanayek wrote:
Hi,

After chaining the translators:

Another problem is that "normal" operations like un-tarring a file are
taking ridiculously long. Here's the NFS performance with the 256k
rsize/wsize mount:

% ( cd /mnt/eon0/tmp ; time tar jxf Python-2.5.2.tar.bz2 ; cd ) &
6.694u 3.538s 0:17.78 57.4%	0+0k 0+0io 0pf+0w

~17 seconds

% ( cd /export/glfs/tmp ; time tar jxf Python-2.5.2.tar.bz2 ; cd ) &
6.544u 1.029s 1:44.44 7.2%	0+0k 0+0io 0pf+0w

~104 seconds

?

Thanks,
Sabuj


_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxx
http://lists.nongnu.org/mailman/listinfo/gluster-devel




[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux