> Let me say it again, if you want to help with that fire up valgrind and see > where the memory is used and eventually leaked. I don't think it's leaked nor have the time atm to inspect it, I just started the thread to see if there was something different done before fork, if that's not the case maybe someone that know the code well could rethink something. Redesigning some bits of Cutelyst to better use --async might scale better on the long go..
Thanks _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
