...
Long-run test reveals comparable memory usage as gunicorn, but there seem to be more knobs to play with. TBC.
One of the things we can do against boundless growth of uwsgi is the use of --reload-on-rss, this kills any worker that exceeds the RSS limit, but results in an empty metadata reply, which is unwanted behaviour. If however, we also supply --lazy, the app is loaded in the worker(s) and the (re)start of each worker then also triggers the reload of metadata. This could be a compromise if the VM is less cpu bound than memory?