On Mon, Feb 3, 2014 at 2:45 PM, Warren Young <warren@xxxxxxxxxxx> wrote:
> On 2/3/2014 13:39, Les Mikesell wrote:
>>
>> A new child process will share almost all
>> memory with the parent, slowly growing as values change.
>
> The trick is to load up as much as possible in the parent before the
> children start forking off.
>
> If the parent does little more than initialize the web stack itself, the
> children don't end up sharing anything app-specific, which can end up
> being a huge waste of RAM.
Even so, modules that have reference-counted variables and objects
will force blocks to copy-on-write as the references change even if
the data values remain unchanged. But, just on general principles
I'd blame mysql or something caching queries or result sets in the
http clients as the real underlying culprit here. I've seen it go
crazy on a 3 table join.
--
Les Mikesell
lesmikesell@xxxxxxxxx
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
