Swift Proxy Server Workers Defaults to a single process
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Christian Schwede |
Bug Description
OpenStack Swift Proxy Server Daemon (swift-
The configured default is a single worker despite the puppet-swift installer (For Newton) showing it should configure more than a single worker (processor count) [0] We should at a minimum, configure more than a single daemon per the Swift General Service Tuning document [1]
You can work around this by passing an additional yaml template into the openstack deploy command to expand the number of workers:
parameter_defaults:
SwiftWorkers: 24
The actual General Service Tuning recommends 2 x physical cpu core count though it mentions further experiments might be necessary if the server shares other services running on it. (Such as our controllers)
Reviewing the configuration for the swift-proxy-server shows it is configured for a single worker by default by being tuned to:
workers = 0
Thus it suggests something is overriding the configuration by the puppet-swift installer.
In actually testing for scalability of Gnocchi processing metrics on instances with a swift storage backend, it has shown that a single swift-proxy worker will peg a single cpu core at 100 instances ( Technically three workers each pegging a cpu core across 3 controllers - ha deployment)
[0] https:/
[1] http://
Changed in tripleo: | |
assignee: | nobody → Christian Schwede (cschwede) |
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Fix proposed to branch: master /review. openstack. org/418029
Review: https:/