Worker processes

[Igor Sysoev]

On Tue, May 06, 2008 at 11:10:59PM -0700, kingler wrote:

> If you have multiple CPUs, you can also try setting the number of
> worker processes to the same number of CPU cores.

It make sense only if nginx eats many CPU time for gzipping or SSL.
Otherwise OS may schedule all workers on single CPU.

> -Liang
> 
> On Tue, May 6, 2008 at 10:56 PM, Dave Cheney <dave at cheney.net> wrote:
> > 1
> >
> >  Unless you are doing a LOT* of static IO, you won't need more than 1 worker
> > process.
> >
> >  Cheers
> >
> >  Dave
> >
> >  * to define a LOT, we serve 1.5m dynamic hits with 32 mongrels over 3
> > machines using 1 nginx worker. Cpu usage, including compression, 5% max.
> >
> >
> >
> >  On 07/05/2008, at 3:37 PM, Jason Lee wrote:
> >
> >
> > > Hello,
> > >
> > > I am running Nginx as a reverse proxy with Mongrel. I haven't been able
> > > to find a clear example of what to set the worker_processes at. I'm
> > > running 10 mongrels and trying to find the sweet spot for Nginx.
> > >
> > > If anyone has any insight in this, it would be appreciated.
> > >
> >
> >
> >

-- 
Igor Sysoev
http://sysoev.ru/en/