Bill Marrs wrote: >> One more piece of advice: I find it easier to tune memory control with >> a single parameter. Setting up a maximum size and a minumum shared >> size is not as effective as setting up a maximum *UNSHARED* size. >> After all, it's the amount of real memory being used by each child >> that you care about, right? Apache::SizeLimit has this now, and it >> would be easy to add to GTopLimit (it's just $SIZE - $SHARED). Doing >> it this way helps avoid unnecessary process turnover. > > > I agree. For me, with my ever more bloated Perl code, I find this > unshared number to be easier to keep a lid on. I keep my apache > children under 10MB each "unshared" as you say. That number is more > stable that the SIZE/SHARED numbers that GTopLimmit offers. But, I have > the GTopLimit sources, so I plan to tweak them to allow for an unshared > setting. I think I bugged Stas about this a year ago and he had a > reason why I was wrong to think this way, but I never understood it.
I don't remember why I was argueing against it :) But in any case, I'll simply add this third option, so you can control it by either SIZE/SHARED or UNSHARED. _____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
