<div dir="ltr">Also, have you specified a block size for dd? The default (512 bytes) is too low for the number of context switches it generates in FUSE. Use a higher block size (64-128KB) and check the throughput.<div><br>
</div><div>Avati</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Oct 25, 2013 at 7:53 AM, Joe Julian <span dir="ltr"><<a href="mailto:joe@julianfamily.org" target="_blank">joe@julianfamily.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Have you brought this up with Red Hat Support? That is what you pay them for.<br>
<div class="im"><br>
<br>
<br>
Jung Young Seok <<a href="mailto:jung.youngseok@gmail.com">jung.youngseok@gmail.com</a>> wrote:<br>
>I've wrote below email. However it seems I missed mail key word rule on<br>
>subject.<br>
>So I'm sending it again.<br>
>Please check the below mail and any response will be helpful.<br>
>Thanks,<br>
>2013. 10. 25. 오후 6:01에 "Jung Young Seok" <<a href="mailto:jung.youngseok@gmail.com">jung.youngseok@gmail.com</a>>님이<br>
>작성:<br>
><br>
><br>
>Dear GlusterFS Engineer,<br>
><br>
>I have questions that my glusterfs server and fuse client<br>
>perform properly on below specification.<br>
><br>
</div>>It can write only *65MB*/s through FUSE client to 1 glusterfs server (1<br>
<div class="im">>brick and no replica for 1 volume )<br>
> - NW bandwidth are enough for now. I've check it with iftop<br>
</div>> - However it can write *120MB*/s when I mount nfs on the same volume.<br>
<div class="im">><br>
>Could anyone check if the glusterfs and fuse client perform properly?<br>
><br>
><br>
>Detail explanations are below.<br>
>=======================================================================<br>
>I've set 4 glusterfs servers and 1 fuse client.<br>
>Each spec is as followings.<br>
><br>
</div>>*Server x 4*<br>
<div class="im">> - CPU : Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz (2 cpu * 4 core)<br>
> - Memory : 32GB<br>
> - HDD (3TB 7.2K RPM SATA x 14 )<br>
> * RAID6(33T)<br>
> * XFS<br>
> - OS : RHS 2.1<br>
> - 4 Gluster Server will be used 2 replica x 2 distributed as 1 volume<br>
> - NW 1G for replica<br>
> - NW 1G for Storage and management<br>
<br>
</div>No need. The fuse client connects to all the servers. Replication happens from the client.<br>
<div class="im"><br>
> - Current active profile: rhs-high-throughput<br>
><br>
</div>>*FUSE Client (gluster 3.4)*<br>
<div class="im">> - CPU : Intel(R) Xeon(R) CPU E5-2640 0 @ 2.50GHz<br>
> - Memory : 32GB<br>
> - OS : CentOS6.4<br>
> - NW 2G for Storage (NIC bonding)<br>
><br>
>All server will be in 10G network. (for now 1G network)<br>
><br>
><br>
>I've tested to check primitive disk performance.<br>
> - on first glusterfs server<br>
>* it can write 870MB/s (dd if=/dev/zero of=./dummy bs=4096 count=10000)<br>
> * it can read 1GB/s (cat test_file.23 > /dev/null )<br>
> - on fuse client (mount volume : 1 brick(1dist, no-replica)<br>
> * it can write 64.8MB/s<br>
> - on nfs client (mount volume : 1 brick(1dist, no-replica)<br>
> * it can write 120MB/s (it reached NW bandwith<br>
<br>
</div>My usual question here is how does dd represent your expected use case? Are you comparing apples to orchards?<br>
<div class="im"><br>
><br>
><br>
>I wonder why fuse client much slower than nfs client. (it's no-replica peer)<br>
>Is it normal performance?<br>
<br>
</div>I always max out my network connection with the fuse client, so no. It's not normal.<br>
<br>
<br>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a></blockquote></div><br></div>