We've recently migrated from Apache which does round-robin distribution to its workers to uWSGI which does it on a first-worker-not-busy basis.
Some parts of our application cache things per-child assuming that that cache isn't going to live for very long, since we have a max request limit per child (implemented with childs doing harakiri) under Apache any given worker wouldn't live for more than 5-10m. But under uWSGI it's possible to have a server with say 16 child procceses, where normally only the first 8 serve requests. So e.g. if you get a daily request peak and use child 9-16 for a a few minutes every day those children will continue to live until the next day, having some per-process cache that's very out of date Is there a way to mitigate this with uWSGI? I haven't found anything like an option to kill stale workers if they're too old. _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
