> Dnia czwartek, 1 grudnia 2011 21:12:25 Roberto De Ioris pisze: >> > Dnia czwartek, 1 grudnia 2011 04:46:25 Roberto De Ioris pisze: >> >> No, workers are forked from the master(). >> > >> > I wanted to verify one thing: when I run with processes = 8 I have 10 >> > workers >> > running: >> > 1x running as root and eats very little memory >> >> this is the jail manager (the /sbin/init equivalent of your main system) >> >> > 1x running as www-data as set in uid/git option, eating less then >> other >> > workers but its memory usage grow over time >> >> this is the master, and if it grows in memory there is a problem/bug. > > I tested it with various options (ksm on/off, chroot on/off, stats > on/off, > diffrent request/memory limits and few more) and with another app > (redmine) to > verify that this is not a bug in my application, and it always happens. My > master process slowly grows under high load, I didn't noticed it when > vassal > is idle. >
Sleeping helped me a bit :) I finally found the last leak in the master popping up during socket logging. My rant on socketpair/epoll was obviously wrong, they helped spotting the leak because their usage in uWSGI was wrong. Now the master will make its health check at regular interval and not every time is is waken up by a event (like remote logging). This should push back master cpu usage to low-values even on event storming and maintain the memory consumption at a static value. The whole thing has been tested with ksm too. Let me know. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
