Nigel Kersten wrote: > On Thu, Apr 30, 2009 at 11:00 AM, Steven Jenkins <[email protected]> wrote: >> Nigel Kersten wrote: >>> so here are my unorganized thoughts on Passenger settings. >>> >> ... >>> * PassengerPoolIdleTime >>> The default is 300 seconds. I'm yet to look into this setting. >>> >>> >> I've done fairly extensive testing over the past few weeks with a Rails app >> on >> Passenger, and I've found the following settings to be very useful in >> improving >> responsiveness: >> >> PassengerPoolIdleTime 0 >> RailsFrameworkSpawnerIdleTime 0 >> RailsAppSpawnerIdleTime 0 >> >> By setting these to zero, no user experiences a 'hang' while the application >> starts up (for the application I was tuning, the startup time could be 5-30 >> seconds, so it was very noticeable and painful). The downside of these is >> that >> memory utilization is not tightly managed (i.e., Passenger never idles out). > > So memory usage is one of our biggest problems with Puppet at the > moment, and application startup time doesn't really affect us much. > > With 2GB of ram on two VCPUs, I'm finding that a pool size of about 12 > is optimal for our configuration. > > That's with 35 environments, each with about: > > 45 modules > 350 files > 200 .pp files (very close to 1:1 mapping of .pp -> class) > around 1000 resources defined, clients getting ~ 300 resource on average. >
Given that, I agree. You probably want to tune PassengerMaxRequests so that you can keep memory usage better under control. I'm thinking mostly of StoreConfigs here. Steven --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
