> On Thu, Apr 4, 2013 at 5:16 PM, Roberto De Ioris <[email protected]> wrote: > >> >> > On Thu, Apr 4, 2013 at 5:06 PM, Roberto De Ioris <[email protected]> >> wrote: >> > >> >> >> >> > Hi, >> >> > >> >> > When I run uwsgi in emperor mode and if threads are set to 0 >> >> "threads=0" >> >> > still there seems to be a thread for each worker. Where is if I run >> >> > without >> >> > emperor mode and set 'threads=0' the worker does not seem to have >> any >> >> > threads. >> >> > >> >> > I have a couple of web instances which are running and I see that >> the >> >> > number of context switches in the machine which has emperor mode >> >> enable >> >> is >> >> > high averages 6k - 8k per second. I would appreciate if someone >> could >> >> shed >> >> > some light on this. >> >> > >> >> > >> >> >> >> uWSGi internally can use threads for various purpose (even if >> >> langiage-specific support for threads is not enabled). >> >> >> >> Are you sure you are not referring to the master process (that is >> >> enabled >> >> automatically when in emperor mode) ? >> >> >> >> >> >> -- >> >> Roberto De Ioris >> >> http://unbit.it >> >> _______________________________________________ >> >> uWSGI mailing list >> >> [email protected] >> >> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >> > >> > >> > >> > When I observe the processes via htop the machine with emperor enabled >> has >> > a child under each worker where as the other machine in which emperor >> mode >> > is disabled I do not see a child under the worker. >> > _______________________________________________ >> > >> >> I do not remember if htop shows threads, but under emperor mode you >> should >> always have an additional process (the master) and 1 child for each >> worker/mule/spooler >> >> >> -- >> Roberto De Ioris >> http://unbit.it >> _______________________________________________ >> uWSGI mailing list >> [email protected] >> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >> > > Htop displays threads and I can see a child for each worker and am > presuming it's a thread. A child for a worker? and I see a child for each > worker only when emperor mode is enabled. >
There are dozens of reason to have additional threads per-worker, expecially when the master is enabled. If you can report your config i could say if it is normal (for example the master has always an additional threads to manage exceptions since 1.9). Maybe you should start the vassal with auto-procname = true and check the output of ps aux -T | grep uWSGI to have a clear view -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
