Vasyl Saienko 3d6557279f Set threads=1 for wsgi applications ...

Due to Python's GIL [1], we can't use multiple threads for running
OpenStack services without a performance penalty, since the execution
ends up serialized, which defeats the purpose.

Instead, we should use several processes, since this approach doesn't
have this limitation.

[1] https://wiki.python.org/moin/GlobalInterpreterLock

This patch updates processes and threads accordingly for:
  aodh
  panko
  nova
  
Related issue was fixed in different deployment tools like puppet
https://bugs.launchpad.net/puppet-keystone/+bug/1602530

Change-Id: Ia8eb4a1f3ed826e206edb94c680f40bcec44e9d7

2019-06-27 09:33:10 +00:00

..

templates

Messaging: use htk function to directly hit RabbitMQ servers

2019-06-18 21:47:45 +00:00

values_overrides

OpenStack: Check Rocky release on Ubuntu Xenial

2019-06-25 21:14:28 +00:00

.helmignore

Add OpenSUSE Leap15 testing

2019-04-15 11:15:35 +02:00

Chart.yaml

Replace git.openstack.org URLs with opendev.org URLs

2019-04-25 00:37:57 +08:00

requirements.yaml

Revert "Update OSH Author copyrights to OSF"

2018-08-28 17:25:13 +00:00

values.yaml

Set threads=1 for wsgi applications

2019-06-27 09:33:10 +00:00