What is the appropriate size for Account and Container servers in Swift? [closed]

asked 2014-05-15 22:40:59 -0600

SamYaple gravatar image

I am considering using SSD for Account and Container servers, with SAS for Object with Swift. I have a few questions.

  • Do Account and Container storage needs grow with the number of Objects, or just accounts and containers?

  • Is there an approriate size ratio for Accounts and Container per 1TB of Object? If so, what is it?

  • What is the data pattern with regards to I/O and throughput for Account and Container servers?

I have been unable to find answers to the questions and would appreciate any help. I would appreciate sources for futher reading if they are available.

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by SamYaple
close date 2014-09-03 16:14:28.638581

1 answer

Sort by ยป oldest newest most voted

answered 2014-06-13 14:53:54 -0600

zaitcev gravatar image

Of course you need more storage to store larger listings of objects in container servers. That's what container servers are for to begin with.

The rule of thumb is to allocate 1..2% of object capacity for A/C. It works pretty well for most cases, but you can bust it by storing gazillions of small objects. Nobody does that because Swift's performance for larger objects is better, so everyone aggregate.

Start by running du on existing a/c directories, then add some for growth.

edit flag offensive delete link more


I dont know how I missed this for so long. Yes I ended up just using some filesystem tools to figure this out.

My use case was actually gazillions of small objects (4MB or so).

I found a balance pretty quick that way. Thank you for your input!

SamYaple gravatar imageSamYaple ( 2014-09-03 16:14:19 -0600 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2014-05-15 22:40:59 -0600

Seen: 483 times

Last updated: Jun 13 '14