Set the WSGI threads=1 And processes/workers to $::processorcount by default

Bug #1602530 reported by Attila Fazekas on 2016-07-13
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Packstack
Undecided
Unassigned
puppet-keystone
Undecided
Alex Krzos

Bug Description

The puppet module WSGI default values a basically useless and just asking for pain.

The WSGI threads behaves as cPhython threads, so they are suffering from the GIL related issues, and usually performer worse when you run more than 1 cpu intensive task at the same time.

The apache itself shields the workers from slow clients, unless you have very slow backed services (mysql) or very slow internal network, keystone will be cpu intensive.

Devstack also uses $subject style, so if you are using a different one just walking on less used path.

On a 8 CPU thread machine the WSGIDaemonProcess line needs to look like:

WSGIDaemonProcess keystone_admin display-name=keystone-admin group=keystone processes=8 threads=1 user=keystone

The treads MUST not be $::processorcount, it needs to be 1 by default.

summary: - Set the WSGI threads=1 snd processes/workers to $::processorcount by
+ Set the WSGI threads=1 And processes/workers to $::processorcount by
default
description: updated
Matt Fischer (mfisch) on 2016-09-24
Changed in puppet-keystone:
status: New → In Progress
assignee: nobody → Alex Krzos (akrzos)
Changed in puppet-keystone:
status: In Progress → Fix Committed
Changed in puppet-keystone:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers