Currently, when you need to synchronize your stack you use a generic lock with
uwsgi.lock() ...critical... uwsgi.unlock() If your app has a lot of critical areas, holding and releasing the same lock over and over again can be overkill for performance. In the current tip you will find a new option --locks <n> allowing you to create <n> additional locks: --locks 3 will allows you to call uwsgi.lock(1) uwsgi.lock(2) uwsgi.lock(3) and obviously uwsgi.unlock(1) uwsgi.unlock(2) uwsgi.unlock(3) Calling uwsgi.lock() and uwsgi.lock(0) will hold the generic (always available) lock. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
