On Tue, Mar 12, 2013 at 6:16 AM, Ashish Kumar <kumar@xxxxxxxxxxx> wrote: > > Hi Guys, > > > > I am configuring CEPH and planning to use just one account for our app. > One schemer will map to one bucket, but before I do this, I need the answer > of following > > questions: > > > > 1) can the number of buckets/account be set to unlimited or a very high > number which is practically not possible to achieve. You can set it to be unlimited (by setting max user buckets to 0). However, note that this is not a recommended setting. The list of buckets per user resides on a single object and is not striped, therefor a really high number would be an issue as you'd end up with unbalanced data allocation. Another issue is that the bucket listing api does not work in chunks, therefor, for every request you'd end up getting the entire list of buckets, which may (and will) cause issues. > > 2) if 1) is yes, then can it degrade the performance if the number of > buckets/account goes really high. Mainly for the second reason that I specified, as bucket listing could clog the system in that case. > > 3) How many buckets/account you suggest. I wouldn't go beyond a few thousands. > > 4) How many objects/bucket you suggest. Hard to say without a proper benchmark. It would be in the millions, but I'm not sure how many millions. Note that currently the main issue is with concurrent writers to the same bucket, as they all update the same index. We have some future plans about how to mitigate this issue, but it'll take some time. > > 5) After what number of objects/bucket performance will start degrading. > Don't really know. Really depending on the leveldb performance at the backend. In my unscientific tests I got to a few millions of objects without a noticeable degradation. But it's really just an anecdotal info. HTH, Yehuda @ http://inktank.com | http://ceph.com _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com