[prev in list] [next in list] [prev in thread] [next in thread] 

List:       uwsgi
Subject:    [uWSGI] Master process
From:       roberto () unbit ! it (Roberto De Ioris)
Date:       2012-10-29 5:37:29
Message-ID: 794aff7788b17f2992e52801e15df221.squirrel () manage ! unbit ! it
[Download RAW message or body]


>
>
> With PHP-FPM it's possible to have a single master process but the workers
> (each with it's own uid/gid and unix socket) don't start until there is a
> request, and after inactivity on those workers they are shutdown.So if I
> have 500 clients, and 400 of those barely get any traffic, my memory is
> not being used with 400 processes that barely get used.
> Is the same possible for uWSGI? It looks to me that if I use Emperor mode
> and have 100 vassles (each with it's own uid/gid and unix socket) then
> each of those 100 vassles will have it's own master process and those 100
> processes ALWAYS running and consuming memory, when all I want is a single
> master process that will start up processes on demand.
> _______________________________________________
> uWSGI mailing list
> uWSGI at lists.unbit.it
> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
>

You have to look at --idle, --cheap and --cheaper options

-- 
Roberto De Ioris
http://unbit.it

[prev in list] [next in list] [prev in thread] [next in thread]