> On Jan 11, 2013, at 6:37 PM, Roberto De Ioris <[email protected]> wrote: > >> Try running with gevent mode + 2 async core (--gevent 2) and start >> blasting the system. If the memory constantly grows someone is leaking, >> otherwise you are simply experimenting huge object allocation on the >> multiple uwsgi/gevent cores/greenlets > > Ok. I did just that. Using gevent 2 this is the GC debug between some > requests: > > gc: objects in each generation: 763 1305 82824 > gc: objects in each generation: 714 3318 128414 > gc: objects in each generation: 761 3999 174227 > gc: objects in each generation: 755 4569 220577 > > In the end I dumped the list of most common types again: > > builtin_function_or_method 63714 > io 62515 > timer 62500 > function 11868 > tuple 4906 > dict 3497 > cell 2806 > list 2036 > weakref 1887 > > > So, it seems someone is leaking. :) I just don't know who for certain > yet... > >
Ok, let'see if it is a gevent-plugin problem. Are this requests generated by uploads ? -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
