Have you tried the 0.25 beta with Passenger? For the life of me I can't get it to work on dapper or hardy.
[ pid=17005 file=ext/common/ApplicationPoolServerExecutable.cpp:307 time=2009-05-04 14:17:27.451 ]: Client 0x667060: SpawnException occured (with error page) and am yet to obtain useful debugging anywhere.... On Mon, May 4, 2009 at 2:07 PM, <ch+...@zeha.at> wrote: > > On Apr 30, 7:20 pm, Nigel Kersten <nig...@google.com> 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. > >> * PassengerStatThrottleRate 600 >> I haven't noticed this make a *huge* difference, but logically we >> don't need to stat for the relevant files at all really. > > I think it's best to actually disable RackAutoDetect & > RailsAutoDetect, but I'm not sure if disabling them will avoid the > stats. > >> * PassengerHighPerformance >> Turning this on appears to reduce performance for me. > > Interesting. From the docs I'm not seeing how this could decrease > performance. Anyway, hosting puppetmaster doesn't need any rewrites or > something, so turning it on/off shouldn't hurt operations. > >> * PassengerMaxRequests >> I'm trying to work out at the moment whether we're leaking memory at >> all with 0.24.8, but even if we're not, I can imagine this making a >> big difference for certain usage patterns. I'm thinking of say having >> a lot of different environments that all puppet regularly, but then an >> overnight period where only one or two environments are being used. If >> I understand how this works correctly, this should reduce memory >> usage. > > This probably depends heavily on your environment. On my setup the > puppetmaster processes stay between 200-300M VIRT, and don't grow > larger, so I haven't looked at this at all. > >> * PassengerPoolIdleTime >> The default is 300 seconds. I'm yet to look into this setting. > > I'm running with the default here, but still get long lived > puppetmaster processes. Probably they never get idle. > >> * RailsSpawnMethod >> * PassengerUseGlobalQueue > > Haven't touched these at all. > > Thanks for your feedback! > > Christian > > > > -- Nigel Kersten nig...@google.com 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 puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
