Hi Roberto, On Thu, 6 Sep 2012 11:42:04 +0200 Roberto De Ioris <[email protected]> wrote:
> --idle <n> simply destroy ALL of the workers while the whole instance > is inactive. I found that out hard way :-(( Any plans to have something more granular eg. on per worker basis ? > If you want to kill single workers after inactivity, just use the > --cheaper option and tune it for your specific needs (via > --cheaper-step and --cheaper-overload) As far as I can see all these options are used to tune uwsgi to quicker react to load spikes and quicker spawn new workers. None of them addresses "how long you want to keep idle workers around" just in case. Seems like with 1.2.x branch there's no way to keep workers around just in case: in my case spawning worker is more expensive than keeping it. > Interesting topics (even if mainly 1.3-related) about 'adaptive > process spawning' > > http://projects.unbit.it/uwsgi/ticket/83 > http://projects.unbit.it/uwsgi/ticket/150 Will keep an eye on these. Thank you Roberto. Marcin _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
