A memory leak is suspected, possibly introduced in january.
On OSM-FR instance, the memory consumed by uvicorn and the child python process is constantly increasing as it can be seen on https://munin.openstreetmap.fr/osm34.openstreetmap.fr/umap.vm.openstreetmap.fr/memory.html
uvicorn gets killed by OOM regularly, almost daily.
To limit this leak effect (worst case is oom-killer killing postgresql):
- add MemoryMax in the systemd service definition
- add limit-max-requests option to uvicorn so that python child are restarted every nth requests
A memory leak is suspected, possibly introduced in january.
On OSM-FR instance, the memory consumed by uvicorn and the child python process is constantly increasing as it can be seen on https://munin.openstreetmap.fr/osm34.openstreetmap.fr/umap.vm.openstreetmap.fr/memory.html
uvicorn gets killed by OOM regularly, almost daily.
To limit this leak effect (worst case is oom-killer killing postgresql):