Why is puppet slow

The solution is to break up the checks into many smaller files. This decreased the number of files in the directory from to The nagios user was unable to read them, causing nagios to refuse to start. Note that though the directory mode argument is set to , puppet understands that when applying this recursively, directories are also supposed to get the execute bit and sets them With these changes in place, after running a few times to get all the files settled into their correct places, the puppet run on spence now takes on average 5 minutes total.

Category : Puppet. Navigation menu Personal tools English Create account Log in. Namespaces Page Discussion. Even without webrick, they still tend to perform poorly.

Certainly something within your environment or its dependencies has changed. Puppet is heavily calling out to tools like facter, package managers, service scripts etc. Any network changes? Do you have a switch plugged into itself? Normal activity? And how many clients are connecting to the server how frequently? One question - does this happen each time you run it on the same box? If there is no new changes - is the performance still terrible or is it only for systems where there is a new change?

I'm just pondering also - did you introduce a new large file? You see the file provider will do an md5 comparison to make sure a a file that already exists doesn't get installed again. If the file is large - then it takes a long time.

Does this slowness happen even when it appears no changes need to be made? If you think a file is a culprit you can emulate the md5 behaviour by running 'time md5sum bigassfile.

Otherwise its the delivery of such a large file I see you have resources or so Webrick at best can manage 1 node concurrently properly. So the minute you fire up more then 1 it will slow down as it tries to serve each client when available. Puppet Users. Ugh, no clue. Is the inode of any directory in its path unusually large?

That will slow down Linux file operations drastically. I found it. Shorewall was rate-limiting. I edited the question to remove the unrelated symptoms. Frank Frank 11 1 1 bronze badge. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name.

Email Required, but never shown. The Overflow Blog. Podcast Explaining the semiconductor shortage, and how it might end. Does ES6 make JavaScript frameworks obsolete? Featured on Meta. Now live: A fully responsive profile.