Memory consumption in case of huge number of configs

[Valentin V. Bartenev]

On Tuesday 19 June 2012 19:42:14 dparshin wrote:
[...]
> > 
> > Of course it creates a new pool. Nginx must
> > continue to work and handle
> > requests, even if it fails to load the new
> > configuration.
> 
> Sounds reasonable, but unused pool(after reload process successfully
> finished) is not destroyed,

Actually it is destroyed. But only after all old workers have finished
servicing their clients.

> and after fork the amount of unused memory
> is multiplied by the number of workers.

The memory used for configuration pool isn't multiplied by the number
of workers because of COW.

 wbr, Valentin V. Bartenev