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 devstack switch to processes to improve performance.
Change-Id: I8cfe9272e098e636441b7cfb51bff08d62c3336e
| ... | ... |
@@ -318,10 +318,10 @@ function configure_keystone {
|
| 318 | 318 |
fi |
| 319 | 319 |
|
| 320 | 320 |
iniset "$KEYSTONE_PUBLIC_UWSGI_FILE" uwsgi wsgi-file "$KEYSTONE_BIN_DIR/keystone-wsgi-public" |
| 321 |
- iniset "$KEYSTONE_PUBLIC_UWSGI_FILE" uwsgi threads $(nproc) |
|
| 321 |
+ iniset "$KEYSTONE_PUBLIC_UWSGI_FILE" uwsgi processes $(nproc) |
|
| 322 | 322 |
|
| 323 | 323 |
iniset "$KEYSTONE_ADMIN_UWSGI_FILE" uwsgi wsgi-file "$KEYSTONE_BIN_DIR/keystone-wsgi-admin" |
| 324 |
- iniset "$KEYSTONE_ADMIN_UWSGI_FILE" uwsgi threads $API_WORKERS |
|
| 324 |
+ iniset "$KEYSTONE_ADMIN_UWSGI_FILE" uwsgi processes $API_WORKERS |
|
| 325 | 325 |
|
| 326 | 326 |
# Common settings |
| 327 | 327 |
for file in "$KEYSTONE_PUBLIC_UWSGI_FILE" "$KEYSTONE_ADMIN_UWSGI_FILE"; do |