<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Ah, ok, that’s what I thought. Then I have no complaints about improved defaults for the fuse case as long as the use case groups retain appropriately optimized settings. Thanks!<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Feb 12, 2019, at 11:14 PM, Raghavendra Gowdappa <<a href="mailto:rgowdapp@redhat.com" class="">rgowdapp@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><br class=""></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Feb 12, 2019 at 11:09 PM Darrell Budic <<a href="mailto:budic@onholyground.com" class="">budic@onholyground.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;" class="">Is there an example of a custom profile you can share for my ovirt use case (with gfapi enabled)? </div></blockquote><div class=""><br class=""></div><div class="">I was speaking about a group setting like "group metadata-cache". Its just that custom options one would turn on for a class of applications or problems.</div><div class=""> <br class=""></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;" class="">Or are you just talking about the standard group settings for virt as a custom profile?<br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Feb 12, 2019, at 7:22 AM, Raghavendra Gowdappa <<a href="mailto:rgowdapp@redhat.com" target="_blank" class="">rgowdapp@redhat.com</a>> wrote:</div><br class="gmail-m_4556511406212266759Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><a href="https://review.gluster.org/22203" target="_blank" class="">https://review.gluster.org/22203</a><br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Feb 12, 2019 at 5:38 PM Raghavendra Gowdappa <<a href="mailto:rgowdapp@redhat.com" target="_blank" class="">rgowdapp@redhat.com</a>> wrote:<br class=""></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" class=""><div dir="ltr" class=""><div class="">All,</div><div class=""><br class=""></div><div class="">We've found perf xlators io-cache and read-ahead not adding any performance improvement. At best read-ahead is redundant due to kernel read-ahead and at worst io-cache is degrading the performance for workloads that doesn't involve re-read. Given that VFS already have both these functionalities, I am proposing to have these two translators turned off by default for native fuse mounts.</div><div class=""><br class=""></div><div class="">For non-native fuse mounts like gfapi (NFS-ganesha/samba) we can have these xlators on by having custom profiles. Comments?<br class=""></div><div class=""><br class=""></div><div class="">[1] <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1665029" target="_blank" class="">https://bugzilla.redhat.com/show_bug.cgi?id=1665029</a></div><div class=""><br class=""></div><div class="">regards,</div><div class="">Raghavendra<br class=""></div></div></div>
</blockquote></div>
_______________________________________________<br class="">Gluster-users mailing list<br class=""><a href="mailto:Gluster-users@gluster.org" target="_blank" class="">Gluster-users@gluster.org</a><br class=""><a href="https://lists.gluster.org/mailman/listinfo/gluster-users" target="_blank" class="">https://lists.gluster.org/mailman/listinfo/gluster-users</a></div></blockquote></div><br class=""></div></blockquote></div></div>
</div></blockquote></div><br class=""></body></html>