worker_process & blockend IO
is at rambler-co.ru
Wed Jul 22 22:48:02 MSD 2009
On Wed, Jul 22, 2009 at 07:38:16PM +0200, Michael Baudino wrote:
> I'm using nginx 0.7.59 on a Debian unstable machine to serve huge files
> (300+ MB) from 2 different filesystems : one is local, the other is
> nfs-mounted over an ADSL link.
> The nfs filesystem is sooooo slow !
> To reduce IO latency, I'm using worker_process 16 (single CPU, though).
> How does nginx handles workers ?
> Does it choose a worker randomly for each connection ?
> Or does it connect to the same worker until it has reached its
> worker_connections limit then connect to the next worker ?
> In that case, should I set a very low worker_connection to force it to
> change worker often ? (I tried it but I got a lot of "worker_connections
> are not enough while connecting to upstream")
workers get connection randomly.
NFS I/O is blocking and it's better to set up second nginx on remote host
and to use proxy:
client > nginx/local fs
/proxy > ADSL > nginx/local fs
More information about the nginx