[Puppet Users] Re: passenger vs mongrel performance

2009-08-24 Thread Larry Ludwig
Hi All,

An update on this thread..

Based upon some real world testing, I've updated the Passenger wiki to  
give some performance and with memory consumption (one of the main  
reasons for switching to Passenger right?):

http://reductivelabs.com/trac/puppet/wiki/UsingPassenger

Let me know if you have any comments, suggestions.

--
Suggested Tweaks

Based upon my (Larry Ludwig) testing of passenger/puppetmasterd I  
recommend adjusting these options in your apache configuration.

PassengerPoolIdleTime - Set to 5 min or less. The shorting this option  
allows for puppetmasterd to get refreshed at some interval. This  
option is also somewhat dependent upon the amount of puppetd nodes  
connecting and at what interval.
PassengerMaxPoolSize - to 15% more instances than what's needed. This  
will allow idle puppetmasterd to get recycled. The net effect is less  
memory will be used, not more.
PassengerUseGlobalQueue on - Since communication with the puppetmaster  
from puppetd is a long process (more than 20 seconds in most cases)  
and will allow for processes to get recycled better
PassengerHighPerformance on - The features Passenger offers with this  
feature disabled are not needed with Puppet.
No different than with traditional web servers, once your service  
starts using swap performance degradation will occur. So be mindful of  
your memory/swap usage on your Puppetmaster.

To monitor the age of your puppetmasterd processes within Passenger, run

passenger-status
the output you should be concerned with is:

...
--- Domains ---
/etc/puppet/puppetmasterd:
   PID: 7355Sessions: 0Processed: 5747Uptime: 1h 3m 30s
   PID: 9950Sessions: 0Processed: 2941Uptime: 27m 27s
   PID: 7117Sessions: 0Processed: 7208Uptime: 1h 8m 33s
   PID: 7575Sessions: 0Processed: 6307Uptime: 57m 19s
   PID: 9653Sessions: 0Processed: 2525Uptime: 37m 31s
My personal preference is I like Passenger recycling puppetmasterd  
every few hours to ensure memory/garbage collection from Ruby is not a  
factor.

-L
--
Larry Ludwig
Reductive Labs


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---



[Puppet Users] Re: passenger vs mongrel performance

2009-07-24 Thread Mark Plaksin

Ohad Levy ohadl...@gmail.com writes:

 Hi All,

 I've recently upgraded all of my mongrels to passenger on all of my
 puppetmasters, and I'm seeing some performance degradations, hopefully
 someone can provide some feedback..

 i see an increase in cpu and load indicators, and i've calculated that the
 actual puppet compile time has increased:
 using mongrels
  - AVG of 3.24515 seconds, out of 30897 config runs
 using passenger
 AVG of 3.53524 seconds, out of 5992 config runs

Once we got our Passenger config options in the right place our compile
time went down by about *2/3*!  Our CPU user stats seem to have gone up
a teensy bit but overall load average is about the same.

To complicate matters (or kill two birds with one stone :), when we
switched to Passenger we also switched to RubyEE.

 the passenger option that i use are:
 PassengerMaxPoolSize 15
 PassengerMaxRequests 3000
 PassengerStatThrottleRate 600

FWIW, here are our options:

PassengerHighPerformance on
PassengerMaxPoolSize 24
PassengerPoolIdleTime 1500
# PassengerMaxRequests 1000
PassengerStatThrottleRate 120
RackAutoDetect Off
RailsAutoDetect Off

We were running 10 puppetmasterds with Mongrel.  With Passenger we
usually see 6-8 running.


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---



[Puppet Users] Re: passenger vs mongrel performance

2009-07-24 Thread Larry Ludwig

Ohad,

Now that we know that passenger is configured in Mark's case, try  
rubyEE and let us know the result.

-L

--
Larry Ludwig
Reductive Labs


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---



[Puppet Users] Re: passenger vs mongrel performance

2009-07-23 Thread Greg

Ohad,

Was discussed a little last month (linky:
http://groups.google.com/group/puppet-users/browse_thread/thread/445bf03568856a0a/36004ff8c56271c3
)

I think the general theme there was that it wasn't as fast as well...
Someone submitted a patch to 0.25 to change the apache2 config example
(linky: http://projects.reductivelabs.com/issues/2430) - seems based
on the fact that it ignores some of the passenger settings if they are
placed within a VirtualHost block...

Greg

On Jul 24, 1:07 pm, Ohad Levy ohadl...@gmail.com wrote:
 Hi All,

 I've recently upgraded all of my mongrels to passenger on all of my
 puppetmasters, and I'm seeing some performance degradations, hopefully
 someone can provide some feedback..

 i see an increase in cpu and load indicators, and i've calculated that the
 actual puppet compile time has increased:
 using mongrels
  - AVG of 3.24515 seconds, out of 30897 config runs

 using passenger
 AVG of 3.53524 seconds, out of 5992 config runs

 the passenger option that i use are:
 PassengerMaxPoolSize 15
 PassengerMaxRequests 3000
 PassengerStatThrottleRate 600

 Thanks,
 Ohad
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---



[Puppet Users] Re: passenger vs mongrel performance

2009-07-23 Thread Ohad Levy
Thanks Greg,

I saw Larrys patch, and its inline with my changes :(

Ohad

On Fri, Jul 24, 2009 at 11:46 AM, Greg greg.b...@gmail.com wrote:


 Ohad,

 Was discussed a little last month (linky:

 http://groups.google.com/group/puppet-users/browse_thread/thread/445bf03568856a0a/36004ff8c56271c3
 )

 I think the general theme there was that it wasn't as fast as well...
 Someone submitted a patch to 0.25 to change the apache2 config example
 (linky: http://projects.reductivelabs.com/issues/2430) - seems based
 on the fact that it ignores some of the passenger settings if they are
 placed within a VirtualHost block...

 Greg

 On Jul 24, 1:07 pm, Ohad Levy ohadl...@gmail.com wrote:
  Hi All,
 
  I've recently upgraded all of my mongrels to passenger on all of my
  puppetmasters, and I'm seeing some performance degradations, hopefully
  someone can provide some feedback..
 
  i see an increase in cpu and load indicators, and i've calculated that
 the
  actual puppet compile time has increased:
  using mongrels
   - AVG of 3.24515 seconds, out of 30897 config runs
 
  using passenger
  AVG of 3.53524 seconds, out of 5992 config runs
 
  the passenger option that i use are:
  PassengerMaxPoolSize 15
  PassengerMaxRequests 3000
  PassengerStatThrottleRate 600
 
  Thanks,
  Ohad
 


--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---