It depends on your cluster, but there are good reasons for doing so. Since Swift's background processes are constantly scanning the drives to check for errors, processes like the object-auditor and object-replicator can clear out the system's page cache simply by scanning the local filesystem's inodes. If you have account and container servers deployed on separate machines from your object servers, requests to an account or container will be more likely to have the data in the local page cache. This can raise the overall object write throughput of your cluster.
--John On Aug 27, 2013, at 6:01 AM, Swift Ops <swift...@bigmir.net> wrote: > Hi, > > Is it good to setup accounts and containers with separated servers, > other than deploying them together with object servers? > > Thanks. > > _______________________________________________ > 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
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ 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
