We have experienced the same issue -- memory leaks -- with our Dancer-based app. Not sure if it's Dancer, underlying Perl, or UWSGI itself, but haven't been able to debug and would certainly appreciate any tips! As a workaround, we use the reload-on-rss option on UWSGI to reload bloated workers. Here's a recipe, with sample settings: processes = 6 # have 6 workers loaded simultaneously reload-on-rss = 800 # if a worker reaches 800MB RSS allocated, reload it after it finishes. harakiri = 120 # (for good measure) hung workers die after 120 seconds The reload-on-rss setting obviously depends on the size of your app, with a bit of headroom for it to bloat until it gets restarted. Make sure (# of processes) * (reload-on-rss) < (available memory). On 3/29/2021 9:39:58 AM, Zahir Lalani <zahirlalani@oliver.agency> wrote: Confidential Hi all Wondering if I can get some guidance. Our application is growing in use and have recently found that UWSGI runs out of worker resources - but when we use uwsgitop, its more that memory has shot up. The only way to resolve is a restart of uwsgi. That sounds like a memory leak, but I am not sure what tools can help me in that regard. I assumed that Perl was quite good at cleanup, but something is not right here. Any guidance appreciated Z _______________________________________________ dancer-users mailing list dancer-users@lists.preshweb.co.uk https://lists.preshweb.co.uk/mailman/listinfo/dancer-users