I get that, but having a cache that over which You have zero control does seems hackish to me. This is of course subjective and there might be cases when this is valid and solid solution. It should be easy to add option that will inform uWSGI about worker max lifetime, specially if this will make someone happy.
2013/1/21 demerphq <[email protected]> > On 21 January 2013 14:41, Łukasz Mierzwa <[email protected]> wrote: > > Why would You need to care about worker age? > > Ill just note that it is a simple way to spoil in-process caches that > scales reasonably nicely. > > Yves > > > -- > perl -Mre=debug -e "/just|another|perl|hacker/" > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > -- Łukasz Mierzwa
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
