Package gem-puma-worker-killer: Information

If you have a memory leak in your web code puma_worker_killer can keep it in
check. Kills pumas, the code kind.

Before you use this gem, know that it is dangerous. If you have a memory issue,
you need to fix the issue. The original idea behind this gem is that it would
act as a temporary band-aid to buy you time to allow you to fix your issues. If
you turn this on and don't fix the underlying memory problems, then things will
only get worse over time.

This gem can also make your performance WORSE. When a worker is killed, and
comes back it takes CPU cycles and time. If you are frequently restarting your
workers then you're killing your performance.

If you have a memory leak in your code, finding and plugging it can be a
herculean effort. Instead what if you just killed your processes when they got
to be too large? The Puma Worker Killer does just that. Similar to Unicorn
Worker Killer but for the Puma web server.

Puma worker killer can only function if you have enabled cluster mode or hybrid
mode (threads + worker cluster). If you are only using threads (and not workers)
then puma worker killer cannot help keep your memory in control.

BTW restarting your processes to control memory is like putting a bandaid on a
gunshot wound, try figuring out the reason you're seeing so much memory bloat
derailed benchmarks can help.

Package gem-puma-worker-killer: Information

Last changed