<div dir="ltr"><div>Hi All,<br></div>Can anyone help me out with this?<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Sep 22, 2020 at 2:59 PM Shreyansh Shah <<a href="mailto:shreyansh.shah@alpha-grep.com">shreyansh.shah@alpha-grep.com</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>Hi,<br></div><div>We are using distributed gluster version 5.10 (7 nodes with 2 bricks per node, i.e 14 bricks total).</div><div><br></div><div>We have set the performance.cache-size parameter as 8GB on server. We assumed that this config parameter indicates the amount of RAM that will be used on the client machine (i.e. upto 8 GB of RAM to be used for data caching at clients). But we observed that on a machine the RAM usage of glusterfs process was around 17GB.</div><div><br></div><div>So we want to know whether our understanding of the parameter is correct? Or something else that we have missed.</div><div><br></div><div>Below are the options configured at glusterfs server, please advise if we can add/tune some parameters to extract more performance.<br><div style="margin-left:40px">storage.health-check-interval: 10<br>performance.client-io-threads: on<br>performance.cache-refresh-timeout: 60<br>performance.cache-size: 8GB<br>transport.address-family: inet<br>nfs.disable: on<br>server.keepalive-time: 60<br>client.keepalive-time: 60<br>network.ping-timeout: 90<br></div></div><div><div><br>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><font face="arial, helvetica, sans-serif">Regards,<br>Shreyansh Shah</font></div></div></div></div></div></div></div></div></div></div>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><font face="arial, helvetica, sans-serif">Regards,<br>Shreyansh Shah</font></div></div></div></div></div></div></div>