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?
Tell me more
×
Server Fault is a question and answer site for
professional system and network administrators. It's 100% free, no registration required.
|
|
|||
|
|
|
evil-reload-* destroy a worker even if in the middle of a request, while the other one wait for request completion |
|||
|