service workers is too high in default

Bug #1582254 reported by Jeffrey Zhang
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kolla
Fix Released
High
Jeffrey Zhang

Bug Description

in default, the number of the workers is equal to the number of the CPU in the server.
this is too high, especially in a 50+ cpu machine. It will bring nothing bug consumer
much cpu and many rabbitmq queue.

Changed in kolla:
assignee: nobody → Jeffrey Zhang (jeffrey4l)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to kolla (master)

Fix proposed to branch: master
Review: https://review.openstack.org/316876

Changed in kolla:
status: New → In Progress
Revision history for this message
Steven Dake (sdake) wrote :

Marking High since this has significant performance impact (reported in the review).

Changed in kolla:
importance: Undecided → High
milestone: none → 2.0.1
milestone: 2.0.1 → newton-1
Changed in kolla:
milestone: newton-1 → newton-2
Changed in kolla:
milestone: newton-2 → newton-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to kolla (master)

Reviewed: https://review.openstack.org/316876
Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=3c3b0288b4d5a20fdab907b210539147a8103820
Submitter: Jenkins
Branch: master

commit 3c3b0288b4d5a20fdab907b210539147a8103820
Author: Jeffrey Zhang <jeffrey.zhang@99cloud.net>
Date: Mon May 16 21:53:16 2016 +0800

    Use a lower number of the workers

    Use a lower number of workers rather than the default value, which is
    equal to the number of the cpu. Otherwise, in a multi cpu environment,
    the number of the processes will very high.

    In this PS, we use min(5, << number of cpu >>) as the default worker
    count.

    Closes-Bug: #1582254
    Change-Id: I1c32cf0db794b43b8fb8be18f39190422ca5846f

Changed in kolla:
status: In Progress → Fix Released
no longer affects: kolla/liberty
no longer affects: kolla/mitaka
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/kolla 3.0.0.0b3

This issue was fixed in the openstack/kolla 3.0.0.0b3 development milestone.

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.