Dnia środa, 30 listopada 2011 21:14:08 Łukasz Mierzwa pisze: > I've noticed that after worker is reloaded due to max-requests, it eats as > much memory as before reload. Reloads caused by editing vassal config file > makes all workers do full restart and they eat very little memory. Should > max requests/max memory limit reloads be technically the same as config > edit reloads? > I think that this is why I got this "worker reload bomb", my workers reached > max memory limit but reload did not caused them to release memory, so they > were reloaded at every request. I just disabled KSM on one node to see if > it makes any difference.
Turning KSM doesn't seem to have any effect and workers used memory is still growing up despite reloads. Workers pid are changing during reload so they are performed. Maybe chroot issue? Łukasz Mierzwa _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
