<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sun, Jul 28, 2013 at 9:57 AM, Marcus Bointon <span dir="ltr"><<a href="mailto:marcus@synchromedia.co.uk" target="_blank">marcus@synchromedia.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div class="im"><div>On 28 Jul 2013, at 18:12, Anand Avati <<a href="mailto:anand.avati@gmail.com" target="_blank">anand.avati@gmail.com</a>> wrote:</div>
<br></div><div class="im"><blockquote type="cite"><div style="font-family:Helvetica;font-size:medium;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">
What is your typical workload, and what kind of tests did you compare native client perf against NFS perf?</div></blockquote><br></div></div><div>Low load, two web servers sharing a content area of < 500M. Even with a single client, performance with native client is slow, i.e. more than about 1 request/sec for a 100k image was enough to make the web server saturate iowait. NFS performance is not amazing, but it's definitely less bad (and there are lots of references in the list archives on NFS being better for small-file performance). Local disk only is orders of magnitude faster. I've not tested whether the performance has improved under 3.4, but frankly having it actually work reliably is more important.</div>
</div></blockquote><div><br></div><div>You might want to give the native client another shot by setting "option max-file-size 128KB" in the quick-read section of the client volfile in /var/lib/glusterd/<volname>/*fuse*.vol (there will be two). Unfotunately this is not settable through the CLI.</div>
<div><br></div><div>Avati</div></div></div></div>