On Nov 7, 2006, at 1:03 PM, Perrin Harkins wrote:
I think some of these are a little over-zealous, Jonathan.
oh, they're completely off the hook. but they work.
BTW, none of my approaches were pre mature optimization. They were
all based on profiling code via Apache::Status to get better
On Tue, 2006-11-07 at 11:35 -0500, Jonathan Vanasco wrote:
> some tips:
I think some of these are a little over-zealous, Jonathan.
> but things like File::Find eat up a TON of memory ( 2+
> mb ), and
> most functionality can be coded in 10-15 minutes. ( vs 2 minutes if
On Nov 7, 2006, at 6:57 AM, Kjetil Kjernsmo wrote:
Exactly what numbers are you then reading out of top then?
Run your app on a clean box -- ie: don't run anything other than
apache/mp ( if you can toss the db onto another service , do it ).
but turn off everything else.
Reboot your mac
On Tuesday 07 November 2006 13:28, Kjetil Kjernsmo wrote:
> > What operating system is it? If linux see
> > http://search.cpan.org/~drolsky/Apache-SizeLimit-0.9/lib/Apache/SizeL
> >imit.pm#linux
>
> Yep, it is GNU/Linux, kernel 2.6.17.
>
> That's very interesting. I hadn't read up on that, because
On Monday 06 November 2006 18:08, Torsten Foertsch wrote:
>
> What operating system is it? If linux see
> http://search.cpan.org/~drolsky/Apache-SizeLimit-0.9/lib/Apache/SizeL
>imit.pm#linux
Yep, it is GNU/Linux, kernel 2.6.17.
That's very interesting. I hadn't read up on that, because I though
On Monday 06 November 2006 19:03, Jonathan Vanasco wrote:
> i've found the reports of shared/unshared memory to be completely
> useless
mmm, OK.
> the only way i've been able to bench memory usage is to run TOP in a
> terminal, and then kill/start apaches with new min_children
> settings, to
