Hi Shri, The short answer is that sharding your data across containers in swift is generally a good idea.
The limitations with containers has a lot more to do with overall concurrency rather than total objects in a container. The number of objects in a container can have an affect on that, but will be less of an issue if you are not putting objects in at a high concurrency. -- Chuck On Sun, Sep 1, 2013 at 9:39 PM, Shrinand Javadekar <shrin...@maginatics.com>wrote: > Hi, > > There have been several articles which talk about keeping the number of > objects in a container to about 1M. Beyond that sqlite starts becoming the > bottleneck. I am going to make sure we abide by this number. > > However, has anyone measured whether putting objects among multiple > containers right from the start gives any performance benefits. For e.g. I > could create 32 containers right at the start and split the objects among > these as I write more and more objects. In the average case, I would have > several partially filled containers instead of a few fully filled ones > (fully filled means having 1M objects). Would this be better for the > overall performance? Any downsides of this approach? Has anyone tried this > before and published numbers on this? > > Thanks in advance. > -Shri > > > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack@lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
