On Tue, May 5, 2009 at 7:20 AM, Steven Jenkins <[email protected]> wrote: > > Nigel Kersten wrote: >> On Mon, May 4, 2009 at 2:07 PM, <[email protected]> wrote: >>> On Apr 30, 7:20 pm, Nigel Kersten <[email protected]> wrote: >>>> so here are my unorganized thoughts on Passenger settings. >>>> >>>> * PassengerMaxPoolSize >>>> >>>> This depends a lot on two primary variables. a) How much RAM you have. >>>> b) How much resident memory is needed for your environments/modules. >>>> Only way to determine this is with tweaking, and you'll need to be >>>> much more conservative than the suggested settings on the Passenger >>>> docs as your app takes up a lot more memory than your average site. >>> Sure; the puppetmaster processes are quite heavy. >>> Right now I'm running with a MaxPoolSize of 10, fitting nicely into >>> the 2.5GB of reserved memory. >> >> I'm finding a similar value works quite nicely in conjunction with setting >> >> PassengerMaxRequests 3000 >> >> Although I'm running with the defaults for idle time of 300 seconds >> anyway, I find that on overnight puppet runs (where we have one >> environment predominantly puppeting, but a few miscellaneous other >> environments also checking in less frequently), this has a significant >> impact upon memory usage. >> >> Without the max requests setting (which for us is about the equivalent >> of 20 puppet runs for that app instance), memory usage continues to >> climb. >> >> I'm not actually seeing memory leaks as such with 0.24.8. What I am >> seeing is that there is a large memory hit for an app instance loading >> a new environment, and that this doesn't necessarily get reclaimed >> quickly enough once that environment is no longer actively used by the >> puppet server. > > You can tune the PassengerPoolIdleTime to a smaller value than the default 300 > seconds to make it reclaim memory faster. Have you experimented any with > that?
Overnight my servers are never ever idle. :) I brought it as low as 10 seconds during heavy periods with almost zero effect. I could do with adding more resources to the servers, but I'm trying to be parsimonious here, and capping max requests does a decent enough job so far. -- Nigel Kersten [email protected] System Administrator Google, Inc. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
