And as an additional note, there is a related bug/feature open for it: http://projects.puppetlabs.com/issues/5650
On Sep 13, 9:49 am, Bart Descamps <barty.desca...@gmail.com> wrote: > I had a similar problem with my nagios server where the catalog run > took about 500seconds for about 100 nodes with about 1000 services, > most of which were generated with exported resources/stored config. We > use the Naginator-resources in puppet. > > However, the main speed issue was not with the fetching of these > resources but with calculating the checksums of all the files I used > (to see if there were changes compared to the master). As was > suggested in the 0.25.x-documentation we put our hosts and our > services in different .cfg-files (in my case we choose to have a file > per host or hostgroup with all of its services included). Yesterday I > changed this however to only a couple of files. In services.cfg for > example all services are kept now... same thing for hosts.cfg, > hostgroups.cfg and commands.cfg. > > My puppetrun now takes about 160 seconds, which is still very slow in > my opinion but a big gain compared to the 500 seconds before. The > compile time has pretty much stayed the same (about 80 seconds), but > at clientside we gained a lot of time. > > Maybe you can try if the same action works for you? > > The MD5-checksum of Puppet seems to be very slow indeed. We also don't > understand why it takes so long, but apparently it does. > > Kind regards, > Bart > > On Sep 13, 8:35 am, Peter Meier <peter.me...@immerda.ch> wrote: > > > > > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > The good thing with this method is that you can manage the module > > > directory (where the different config file excerpts are stored) with > > > 'purge => true' so that only exported resources are present in the final > > > nagios configuration (something that native types don't handle very well > > > -- or actually handle very badly). > > > Yes, because purging the directory would unexport the resource of the > > decomissioned host. But, as other resources might have been exported as > > well, that can't be purged by that trick, I would still recommend to > > clean up decommissioned hosts with the "puppet node clean" face-action, > > that got partially merged into 2.7.3 and hopefully will be fully (with > > the important parts for our discussion) merged into 2.7.4. > > > ~pete > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.4.11 (GNU/Linux) > > Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.org/ > > > iEYEARECAAYFAk5u+bAACgkQbwltcAfKi39iQQCeIf2CPVgA3f11wE0VxPCefZDb > > OvEAn1Tw5UTSTnons6wJGyqUdO50lspD > > =c84z > > -----END PGP SIGNATURE----- -- 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.
