Change the num_engine_workers to greater than current 1

Bug #1434339 reported by Angus Salkeld
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Medium
Angus Salkeld

Bug Description

Now that we have decouple-nested merged, it makes sense to enable more workers.

Also taking this into account (http://httpd.apache.org/docs/current/mod/prefork.html)
one of the limiting factors can be memory. Given that our gate machines might be
memory constrained, let's just do 2 in the gate.

Angus Salkeld (asalkeld)
Changed in heat:
assignee: nobody → Angus Salkeld (asalkeld)
status: New → Triaged
importance: Undecided → Medium
milestone: none → kilo-rc1
Revision history for this message
Steve Baker (steve-stevebaker) wrote :

but to be clear, what we set our config default should be appropriate for production, so 4 might make a good default.

Changed in heat:
status: Triaged → In Progress
Revision history for this message
Angus Salkeld (asalkeld) wrote :
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to heat (master)

Reviewed: https://review.openstack.org/165396
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=8c5b3589e2a3ff11a25f5bf2cf9ad8cff7c8dbdf
Submitter: Jenkins
Branch: master

commit 8c5b3589e2a3ff11a25f5bf2cf9ad8cff7c8dbdf
Author: Angus Salkeld <email address hidden>
Date: Tue Mar 31 07:55:18 2015 +1000

    Change the default num_engine_workers to get_worker_count()

    Now that we have decouple-nested merged, it makes sense
    to enable more workers. oslo has a function just for this
    processutils.get_worker_count()

    Also set the number to 2 for functional tests to
    not overly consume too much memory but still test
    the multi worker path.

    Change-Id: I86d1e8bb1813ccdee959f7a0fe78867dde7d21b5
    Closes-bug: 1434339

Changed in heat:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in heat:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in heat:
milestone: kilo-rc1 → 2015.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.