what a worker does?
paul at gtcomm.net
Tue Jul 1 01:31:42 MSD 2008
Well that's what I consider multithreaded I guess.. It doesn't use any
more processes or scheduling time to handle multiple connections where
as apache is multi process.. I guess i consider multithreaded the
ability to handle multiple instances within the same process without
creating new processes (having 50000 open connections to the same
process wether it's network, disk, etc). Maybe that is the wrong word
> On Monday 30 June 2008, Paul wrote:
>> A worker is a process of nginx.. Each process is multithreaded and can
> nope, no threads
> Asynchronous I/O for network and blocking I/O for disk access
>> handle thousands of connections each.
>> You can have one worker and 50,000 connections to it, but it's good to
>> have at least as many workers as you have CPUs and I usually multiply
>> this times 4 (so 4 worker per CPU)..
>> Worker connections is how many connections each process (worker) can
>> have open at one time (max files open, sockets, etc)
More information about the nginx