<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 20, 2016 at 3:24 PM, Gandalf Corvotempesta <span dir="ltr"><<a href="mailto:gandalf.corvotempesta@gmail.com" target="_blank">gandalf.corvotempesta@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">2016-09-20 10:28 GMT+02:00 Pranith Kumar Karampuri <<a href="mailto:pkarampu@redhat.com">pkarampu@redhat.com</a>>:<br>
> Are you willing to take VM snapshots at the right times?<br>
<br>
</span>Yes, sure.<br>
<br>
In addition, the same cluster would also be used to store files shared<br>
between webservers, like the uploaded images and so on.<br></blockquote><div><br></div><div>I would suggest to use separate volumes for this, because the optimizations for VM image store on the volume would slow things down for webservers kind of workload IMHO. Most of the perf xlators should be disabled in VM image store usecase.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
> Please don't use EC for Random write workload, it is better for extending<br>
> write workload at the moment. Replica 3/Arbiter is what I would suggest.<br>
<br>
</span>With replica 3/arbiter do you mean 3 hosts in replica plus an arbitrer<br>
or 2 hosts in replica plus an arbiter?<br>
</blockquote></div><br>2hosts in replica plus arbiter.<br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Pranith<br></div></div>
</div></div>