5

What is the difference between reload-on-as and evil-reload-on-as options in uwsgi config?
I use reload-on-as and uwsgi worker still consumes unlimited memory and reloads when task is finished. I need to kill worker when it consumes limited memory for debug purposes. What is the best way to do it? May be limit-as option?

Improve this question

1 Answer 1

Reset to default
4

evil-reload-* destroy a worker even if in the middle of a request, while the other one wait for request completion

Improve this answer
1
  • Thanks. Now it is clear how it should work, but it doesn't work for me (uwsgi-python). Workers still can consume unlimited memory with evil-reload-*.
    – Raz
    Nov 13, 2012 at 14:36

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .