openstack
/
charm-octavia
Code Issues Proposed changes

Drop wsgi thread configuration to a single thread 

We should increase concurrency using processes rather than threads
for the Octavia WSGI application, avoiding high memory consumption
over time under load.

Change-Id: Ia4b0e6b6b364dc3c9cd2fa4cdfa93cd2766c4d6a
Closes-Bug: #1806008
This commit is contained in:
Frode Nordahl 2018-12-06 05:42:39 +01:00
parent cc464bc38c
commit 1a577cea6e
No known key found for this signature in database
GPG Key ID: 6A5D59A3BA48373F
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/templates/rocky/octavia-api.conf
View File

@ -5,7 +5,7 @@ Listen {{ options.service_listen_info.octavia_api.public_port }}
# See https://cryptography.io/en/latest/faq/#starting-cryptography-using-mod-wsgi-produces-an-internalerror-during-a-call-in-register-osrandom-engine
<VirtualHost *:{{ options.service_listen_info.octavia_api.public_port }}>
WSGIDaemonProcess octavia-api user=octavia group=octavia processes=3 threads=10
WSGIDaemonProcess octavia-api processes={{ options.wsgi_worker_context.processes }} threads=1 user=octavia group=octavia display-name=%{GROUP}
WSGIProcessGroup octavia-api
WSGIApplicationGroup %{GLOBAL}
WSGIScriptAlias / /usr/bin/octavia-wsgi