[Bug 1665270] Re: Lower number of workers by default

Ryan Beisner 1665270 at bugs.launchpad.net
Thu Feb 16 12:19:54 UTC 2017


+1 to the need for this.  I think we should consider adding a cap as a
config option.

This is an issue in testing and publishing bundles that are one-size-
fits-all.  For example, the openstack-base or openstack-on-lxd bundles
may work great on 8c or 16c boxes, but require tuning down max workers
for ~7 charm applications on machines with 48c so as not to OOM the
hosts.

One alternative/additive view is that Juju should implement container
resource limits.  I agree that is needed for this and other reasons.
However, that wouldn't give the max workers cap tunable that is desired
here.

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to cinder in Juju Charms Collection.
Matching subscriptions: charm-bugs
https://bugs.launchpad.net/bugs/1665270

Title:
  Lower number of workers by default

Status in Charm Helpers:
  New
Status in cinder package in Juju Charms Collection:
  New
Status in glance package in Juju Charms Collection:
  New
Status in heat package in Juju Charms Collection:
  New
Status in keystone package in Juju Charms Collection:
  New
Status in neutron-api package in Juju Charms Collection:
  New
Status in neutron-gateway package in Juju Charms Collection:
  New
Status in nova-cloud-controller package in Juju Charms Collection:
  New

Bug description:
  On containerized setups with multiple cpus and hyperthreading on the
  metals the containers can see a large number of cores. With the
  default worker multiplier settings this eg. results in 112 workers
  plus a leader processes on one of our installs. With HA we have then
  3x113 processes serving in total, which is a bit of a waste (3x16G of
  RSS for one service, as an example)

  While this can be tuned down I'd suggest to cap the number of workers
  when the worker-multiplier setting is on default to make this more
  sensible out of the box

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-helpers/+bug/1665270/+subscriptions



More information about the Ubuntu-openstack-bugs mailing list