John ORourke wrote:
Might be showing off my lack of unix admin knowledge here but using
'top', it's the value of the 'virt' column - ie. the biggest possible
process size if the whole thing was resident. I've been using it to
work out how many clients I should limit apache to, but looking at i
Roberto C. Sánchez wrote:
On Fri, Feb 22, 2008 at 09:52:30AM +, John ORourke wrote:
Mine start at around 60MB, jump to 80MB when my app is initialised, and
can peak at 120MB during their lifetime. For reference I tried making
the tiniest possible one with everything stripped out, and th
On Fri, 2008-02-22 at 09:52 +, John ORourke wrote:
> Hi folks,
>
> I'm trying to make my apache processes as small as possible, and one
> thing I find lacking in optimisation guides is actual real world process
> sizes.
>
> So... how big is yours? ;)
I'm running on 32-bit linux 2.6, using
On Fri, Feb 22, 2008 at 09:52:30AM +, John ORourke wrote:
> Hi folks,
>
> I'm trying to make my apache processes as small as possible, and one
> thing I find lacking in optimisation guides is actual real world process
> sizes.
>
> So... how big is yours? ;)
>
> Mine start at around 60MB, j
Hi folks,
I'm trying to make my apache processes as small as possible, and one
thing I find lacking in optimisation guides is actual real world process
sizes.
So... how big is yours? ;)
Mine start at around 60MB, jump to 80MB when my app is initialised, and
can peak at 120MB during their li
