You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Boysenberry Payne <bo...@humaniteque.com> on 2005/11/05 21:06:59 UTC
Questions about memory
Now that I'm at the tail end of my current project (not necessarily the
best time to tackle
this issue I know) I'm looking at my httpd processes using top:
PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD RSIZE
VSIZE
16970 httpd 0.0% 0:00.01 1 9 247 108K 17.5M 1.32M
60.1M
16961 httpd 0.0% 0:00.00 1 9 247 108K 17.5M 1.30M
60.1M
16960 httpd 0.0% 0:00.01 1 9 247 108K 17.5M 1.30M
60.1M
16959 httpd 0.0% 0:00.69 1 9 256 1.64M 17.4M 6.24M
61.1M
16958 httpd 0.0% 0:01.07 1 9 278 2.33M 17.4M 7.64M
61.1M
16957 httpd 0.0% 0:01.23 1 9 291 3.96M 17.7M 13.0M
63.5M
13220 httpd 0.0% 0:28.69 1 9 247 32K 17.5M 11.6M
60.1M
It gives a selection of used and non-used children (as well as root
13220.)
Are they memory intensive? I know it depends on the CPU, RAM, etc...
But what is big nowa days? Am I looking at this with the wrong tool?
Basically I'm looking for pointers on how to tighten things up. I'm
hoping
to use this in a production environment and need to know when I need to
scale
things up.
I'm a novice when it comes to memory management, sorry. So as much
as as anyone can provide is much appreciated.
Thanks,
Boysenberry
boysenberrys.com | habitatlife.com | selfgnosis.com
Re: Questions about memory
Posted by Jonathan <jv...@2xlp.com>.
get a copy of the mod perl book on oreilly
this chapter is invaluable:
http://www.modperlbook.org/html/part2.html
read through it online or in the book. it'll answer most of your
questions.
On Nov 5, 2005, at 3:06 PM, Boysenberry Payne wrote:
> Now that I'm at the tail end of my current project (not necessarily
> the best time to tackle
> this issue I know) I'm looking at my httpd processes using top:
>
> PID COMMAND %CPU TIME #TH #PRTS #MREGS RPRVT RSHRD
> RSIZE VSIZE
> 16970 httpd 0.0% 0:00.01 1 9 247 108K 17.5M
> 1.32M 60.1M
> 16961 httpd 0.0% 0:00.00 1 9 247 108K 17.5M
> 1.30M 60.1M
> 16960 httpd 0.0% 0:00.01 1 9 247 108K 17.5M
> 1.30M 60.1M
> 16959 httpd 0.0% 0:00.69 1 9 256 1.64M 17.4M
> 6.24M 61.1M
> 16958 httpd 0.0% 0:01.07 1 9 278 2.33M 17.4M
> 7.64M 61.1M
> 16957 httpd 0.0% 0:01.23 1 9 291 3.96M 17.7M
> 13.0M 63.5M
> 13220 httpd 0.0% 0:28.69 1 9 247 32K 17.5M
> 11.6M 60.1M
>
> It gives a selection of used and non-used children (as well as root
> 13220.)
>
> Are they memory intensive? I know it depends on the CPU, RAM, etc...
> But what is big nowa days? Am I looking at this with the wrong tool?
>
> Basically I'm looking for pointers on how to tighten things up.
> I'm hoping
> to use this in a production environment and need to know when I
> need to scale
> things up.
>
> I'm a novice when it comes to memory management, sorry. So as much
> as as anyone can provide is much appreciated.
>
> Thanks,
> Boysenberry
>
> boysenberrys.com | habitatlife.com | selfgnosis.com
>