Keystone uwsgi performance tuning

I ran some tests locally that showed that when using the uwsgi
deploy the keystone server wasn't using all the processes
available. When I switched from "threads" to "processes" the
concurrent performance improved considerably. So I'm proposing
that the docs use processes to improve performance.

Change-Id: I5375702f45ccb82c02ff2bba1eabda836d5d25eb
This commit is contained in:
Brant Knudson 2016-06-03 16:01:29 -05:00
parent bb16415bac
commit d03ed967dd
3 changed files with 4 additions and 4 deletions

View File

@ -66,8 +66,8 @@ Start or restart HTTPD to pick up the new configuration.
Now configure and start the uwsgi services. Copy the Now configure and start the uwsgi services. Copy the
`httpd/keystone-uwsgi-admin.ini` and `httpd/keystone-uwsgi-public.ini` files to `httpd/keystone-uwsgi-admin.ini` and `httpd/keystone-uwsgi-public.ini` files to
`/etc/keystone`. Update the files to match your system configuration (for `/etc/keystone`. Update the files to match your system configuration (for
example, you'll want to set the number of threads for the public and admin example, you'll want to set the number of processes and threads for the public
servers). and admin servers).
Start up the keystone servers using uwsgi:: Start up the keystone servers using uwsgi::

View File

@ -14,7 +14,7 @@ master = true
enable-threads = true enable-threads = true
# Tune this to your environment. # Tune this to your environment.
threads = 4 processes = 4
# uwsgi recommends this to prevent thundering herd on accept. # uwsgi recommends this to prevent thundering herd on accept.
thunder-lock = true thunder-lock = true

View File

@ -14,7 +14,7 @@ master = true
enable-threads = true enable-threads = true
# Tune this to your environment. # Tune this to your environment.
threads = 4 processes = 4
# uwsgi recommends this to prevent thundering herd on accept. # uwsgi recommends this to prevent thundering herd on accept.
thunder-lock = true thunder-lock = true