Description of problem: Description of problem: In OSP14, swift has number of workers set to number of cores for all its services like swift-proxy-server, swift-account-server, swift-container-server, swift-object-server. On a 56 cores machines, we have 57 swift-proxy-server processes for example. Ideally we should cap workers at min(cpu-cores/2, 12) Version-Release number of selected component (if applicable): OSP13 How reproducible: 100% Steps to Reproduce: 1. deploy director with defaults 2. 3. Actual results: Too many swift processes Expected results: Max of 12 swift workers Additional info: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
*** This bug has been marked as a duplicate of bug 1647510 ***
This can be also set by using some extra parameters during deployment, for example: parameter_defaults: SwiftWorkers: 12 SwiftAccountWorkers: 12 SwiftContainerWorkers: 12 SwiftObjectWorkers: 12
Christian, But shouldn't we shipping with more conservative defaults?
*** Bug 1651678 has been marked as a duplicate of this bug. ***
(In reply to Sai Sindhur Malleni from comment #6) > Christian, > > But shouldn't we shipping with more conservative defaults? Yes, for future versions we should do this and we can change the default. However, as mentioned earlier this might have a severe impact on customers if we change the default for an already shipped product and it gets applied automatically during an upgrade. In that case please use a different default like written in https://bugzilla.redhat.com/show_bug.cgi?id=1651680#c3
Christian, This bug is for OSP14 and we haven't yet shipped OSP14 right?
Closing EOL, OSP 15 has been retired as of Sept 19, 2020