How many objects can be contained at one-container

The concern is that a single container db that is handling all of these objects. Each update (new object) then has to update the container. These updates get slower as the container gets larger (the fixed cost of the btree update for each object PUT gets larger). Object reads, however, are unaffected (because they don't even touch the container db).

We recommend that you shard large containers and aim for about 10 million objects in each if you are running account and containers servers on standard hard drives. At large scale, running your account and container servers on boxes with fast IO can also improve things dramatically. For example, in internal tests, we've seen containers with a billion rows still handle 400 updates a second when they have fast IO (read: SSDs).

--John

On Jun 30, 2011, at 11:05 PM, Ted,Jung wrote:

> New question #163356 on OpenStack Object Storage (swift):
> https://answers.launchpad.net/swift/+question/163356
>
> To anyone
>
> Let us suppose
> Some service have 10mil users
> Each user generates 10 objects everyday
>
> If 10 mil users mapped to just one swift user
> If The swift user have one container
>
> Each day 100 mil objects are stored to just one container
>
> In this case, what is the problem
> Is this right thing or not?
>
> --
> You received this question notification because you are a member of
> Swift Core, which is an answer contact for OpenStack Object Storage
> (swift).
> This email may include confidential information. If you received it in error, please delete it.