<div dir="ltr"><div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Fri, Oct 5, 2018 at 1:54 AM Tyler Salwierz <<a href="mailto:tyler@irex.me">tyler@irex.me</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">Hi,<div><br></div><div>I have a server setup on a powerful processor (i7-8700). I have three bricks setup on localhost - each their own hard drive. When I'm downloading content at 100MB/s I see upwards of 180% CPU usage from GlusterFS.</div><div><br>Uploading content at 100MB/s is much more manageable, with around 50%-70% cpu usage combined from all the glusterfs processes.</div></div></div></blockquote><div><br></div><div>Do you see the high CPU usage of clients and bricks?</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div><br></div><div>My question is, is this normal CPU usage? I thought GlusterFS was designed to be used in a RAID configuration with having an internal network setup with upwards of 20Gbps connectivity per node. If 1Gbps write speed is causing 180% cpu usage on only three hard drives/bricks, how could a raid setup at 20Gbps possibly be feasible?</div></div></div></blockquote><div><br></div><div>This looks to be an anomaly, especially with reads/writes. Is it possible to attach output of "top -bHd >> top.txt"?</div><div><br></div><div>Also recently there was a similar thread (though the issue was not resolved)</div><div><a href="https://lists.gluster.org/pipermail/gluster-users/2018-July/034414.html">https://lists.gluster.org/pipermail/gluster-users/2018-July/034414.html</a><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div><br></div><div>This is a default distributed volume. Just the standard 3-4 commands to get the volume created, started and running. There has been no additional tuning done.</div></div></div>
_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a><br>
<a href="https://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">https://lists.gluster.org/mailman/listinfo/gluster-users</a></blockquote></div></div></div>