Do you have write-behind loaded on the client side? For IO testing, use /dev/zero instead of /dev/urandom. avati On Fri, Jan 23, 2009 at 2:14 AM, Evan <_Gluster at devnada.com> wrote: > I have a 2 node single process AFR setup with 1.544Mbps bandwidth between > the 2 nodes. When I write a 1MB file to the gluster share it seems to AFR to > the other node in real time killing my disk IO speeds on the gluster mount > point. Is there anyway to fix this? Ideally I would like to see near real > disk IO speeds from/to the local gluster mount point and let the afr play > catch up in the background as the bandwidth becomes available. > > Gluster Spec File (same on both nodes) http://pastebin.com/m58dc49d4 > IO speed tests: > # time dd if=/dev/urandom of=/mnt/gluster/disktest count=1024 bs=1024 > 1024+0 records in > 1024+0 records out > 1048576 bytes (1.0 MB) copied, 8.34701 s, 126 kB/s > > real 0m8.547s > user 0m0.000s > sys 0m0.372s > > # time dd if=/dev/urandom of=/tmp/disktest count=1024 bs=1024 > 1024+0 records in > 1024+0 records out > 1048576 bytes (1.0 MB) copied, 0.253865 s, 4.1 MB/s > > real 0m0.259s > user 0m0.000s > sys 0m0.284s > > > Thanks > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://zresearch.com/cgi-bin/mailman/listinfo/gluster-users > >
