9 messages in ru.sysoev.nginxRe: what a worker does?
FromSent OnAttachments
Marcos NevesJun 30, 2008 10:46 am 
PaulJun 30, 2008 2:08 pm 
RoxisJun 30, 2008 2:12 pm 
Mark FosterJun 30, 2008 2:27 pm 
PaulJun 30, 2008 2:31 pm 
PaulJun 30, 2008 2:59 pm 
MichaelJun 30, 2008 3:29 pm 
ThomasJul 1, 2008 2:06 am 
RoxisJul 1, 2008 2:41 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: what a worker does?Actions...
From:Mark Foster (mfos@public.gmane.org)
Date:Jun 30, 2008 2:27:32 pm
List:ru.sysoev.nginx

Paul wrote:

A worker is a process of nginx.. Each process is multithreaded and can 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)

I would like to know if this really makes more sense that just using 1-to-1 workers to CPUs. Have you done any benchmark to determine the 4-to-1 ratio gives better performance? What is the "best practice?" Thanks.