> 2011/2/14 Roberto De Ioris <[email protected]>: >> >> If i remember correctly you run with full logging disabled (so reporting >> it in the logs would be useless). Maybe the master can print the >> 'percent' >> variation ? Something like >> >> *** listen queue is now 10 % full >> *** listen queue is now 20 % full >> *** listen queue is now 10 % full >> *** listen queue is now 30 % full >> >> or you want to manage it in the code accessing something like >> env['uwsgi.listen_queue'] ? > > Yes I'd like to manage it with something like > uwsgi.stats['listen_queue']. A 'stats' dictionary in the uwsgi module > sounds better than WSGI variables. > -- > Jean-Baptiste Quenot >
Sadly i cannot go (for now) with dictionaries as in threading mode they get clobbered (and i do not want to add another lock in the stack ;) ) I will export a uwsgi.listen_queue() function that will return the value taken from a shared area (no locking needed as the value is updated only by master) -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
