On 10/03/10 18:58, Douglas Garstang wrote: > We have puppet 0.24.8 running on multiple EIGHT core 3.16Ghz servers > with 32Gb of RAM, and in each case puppet is taking longer and longer > to run, as we have it control more. Currently it's taking up to 20 > minutes to perform a run. > > What approaches can I take to significantly reduce the time it takes > puppet to run? It's ALSO sucking up an inordinate amount of CPU while > it performs a run. The server is using passenger.
Where do you experience the issue: on the clients or on the master? 0.25 highly improved the master performance and file serving. High cpu usage on the client is highly dependent on what you are managing (ie most of the time is usually spent in other processes than puppet, like package manager). Something that also can stress clients is managing deep file hierarchies. For high cpu usage on the master, you can try to: * disable storeconfigs or use thin_storeconfigs (0.25) * make sure your clients sleep longer than the default or use splay times so they don't ask their catalogs at the same time * use a different ruby interpreter, and/or passenger * if you're doing tons of file serving, offload those to a static server (see my last blog article in my signature). This will free your masters to serve more catalogs per unit of time. Hope that helps, -- Brice Figureau My Blog: http://www.masterzen.fr/ -- 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.
