Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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?

share|improve this question
up vote 1 down vote accepted

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

share|improve this answer
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 '12 at 14:36

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.