mirror of https://github.com/searxng/searxng.git
e28a69515c
As stated in .. and other posts, the defaults of uWSGI not suitable for a productive environment. To give just one example, the workers run indefinitely and the memory leaks aggregate. - "Configuring uWSGI for Production: The defaults are all wrong" EuroPython 2019 [1] - "Configuring uWSGI for Production Deployment" [2] - "When Paul has tested some PR on his instance, we could clearly see a memory leak over a week: the memory never dropped to the initial value. Same for my instance using Docker." [3] [1] https://av.tib.eu/media/44810 [2] https://www.bloomberg.com/company/stories/configuring-uwsgi-production-deployment/ [3] https://github.com/searxng/searxng/pull/3443#issuecomment-2094347004 Signed-off-by: Markus Heiser <markus.heiser@darmarit.de> |
||
|---|---|---|
| .. | ||
| httpd/sites-available | ||
| nginx/default.apps-available | ||
| searxng | ||
| uwsgi | ||
| apache2 | ||