<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Thanks Amar, so what are the hard limits of Gluster as far as number of directories and files in directories and i-nodes?<div><br></div><div><br><div><div>On Jan 12, 2012, at 3:41 AM, Amar Tumballi wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
We are evaluating Gluster as the filesystem for a large scale web application where users upload many images. I wanted to see what are the limitations of Gluster as far as number of files/directories and more importantly what are some best practices?<br>
<br>
We are thinking of using distributed + replicated mode with 3 copies of each file. Is that the best approach?<br>
<br></blockquote><div>Best option for number of copies is 2 (considering the performance), but if your use case requires 3 copies, then that should work fine too. But modification/creation time would be more with replica count 3.<br>
</div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
In addition, how should we store the files, can we have one huge flat namespace (i.e. UUIDs for names) or should we have a hierarchical directory structure just like a regular filesystem to distribute the files into many sub-directories?<br>
<br></blockquote><div>We recommend using directory structure as regular filesystem, because having millions of files in a same directory would make the directory listing/crawling operation to perform poorly.<br> <br></div>
</div><br>Regards,<br>Amar<br>
</blockquote></div><br></div></body></html>