Red Hat Bugzilla – Bug 1313368
keystone wsgi default worker number threads vs. processes
Last modified: 2016-04-18 02:44:55 EDT
Description of problem:
Puppet keystone default the number of python threads to the number of processors,
instead of setting processes to nr_cpu and leave the threads to 1.
Version-Release number of selected component (if applicable):
$ cat /etc/httpd/conf.d/10-keystone_wsgi_admin.conf |grep thread
WSGIDaemonProcess keystone_admin display-name=keystone-admin group=keystone processes=1 threads=4 user=keystone
WSGIDaemonProcess keystone_admin display-name=keystone-admin group=keystone processes=4 threads=1 user=keystone
cat /proc/cpuinfo |grep process | wc -l
It will lead to little more memory usage,
but you will be able utilize the cpu.
If the DB in LAN range, you should not try to increase the number of threads by default.
Attila, thanks for your bug report.
Since we're using Launchpad to track bugs in upstream projects, it would be very nice to report this bug in https://bugs.launchpad.net/puppet-keystone
Also, if you think that's a bug in OSP Director, you might want to create a bug for TripleO Heat Templates to change the values.