Public bug reported:

The docs recommend setting the 'workers' option equal to the number of
CPUs on the host but defaults to 1.  I proposed a change to devstack to
set workers=`nproc` but it was decided to move this into glance itself:

https://review.openstack.org/#/c/99739/

Note that nova changed in Icehouse to default to number of CPUs
available also, and Cinder will most likely be doing the same for it's
osapi_volume_workers option.

This will have a DocImpact and probably UpgradeImpact is also necessary
since if you weren't setting the workers value explicitly before the
change you'll now have `nproc` glance API workers by default after
restarting the service.

** Affects: glance
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1333325

Title:
  glance-api workers should default to number of CPUs available

Status in OpenStack Image Registry and Delivery Service (Glance):
  New

Bug description:
  The docs recommend setting the 'workers' option equal to the number of
  CPUs on the host but defaults to 1.  I proposed a change to devstack
  to set workers=`nproc` but it was decided to move this into glance
  itself:

  https://review.openstack.org/#/c/99739/

  Note that nova changed in Icehouse to default to number of CPUs
  available also, and Cinder will most likely be doing the same for it's
  osapi_volume_workers option.

  This will have a DocImpact and probably UpgradeImpact is also
  necessary since if you weren't setting the workers value explicitly
  before the change you'll now have `nproc` glance API workers by
  default after restarting the service.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1333325/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to