Thanks a lot, Roberto, for a fast and helpful response. Indeed, lazy-apps helps quite a bit! It was around 20 MB for the master process and now 7.9MB. Unfortunately, my cloud provider's Linux kernel does not have KSM enabled. Still, that's a measurable improvement!
On Wed, Mar 6, 2013 at 8:03 PM, Roberto De Ioris <[email protected]> wrote: > > > Hi, everyone, > > > > I have a *multi-app deployment for a SASS service*, where every one of my > > clients has his own database and application instance (a separate django > > settings.py file). > > > > This requires creating a separate uWSGI ini file for each client. > > > > I am currently running uWSGI in emperor mode. > > > > Even when enabling *"cheap" *and *"idle" *for the vassals*, *there is a > > process running for each one of them, even in idle mode. > > > > I have some amount of *stale clients* which use the service only > > occasionally and I would like their apps (vassals) not to consume any > > resources in idle mode, trading off some start-up time. > > > > What is your advice on how to achieve this? Is there a way to achieve > this > > with uWSGI? > > > > Thanks! > > > > Regards, > > Igor Katson. > > > > The process you are seeing is the master. It is required to have it to > maintain the socket binding. > > You can highly reduce memory usage of masters in that way: > > add lazy-apps = true > > it means the application code is not loaded in the master but only on the > workers. > > If you are on linux, enable ksm, in my tests, a master without an app > loaded can consume less that 8 pages of memory. > > > -- > Roberto De Ioris > http://unbit.it > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
