On 22/05/11 01:10, Gabriel Filion wrote: > Hello, > > I found out that a puppetmaster I manage is currently not using the > thin_storeconfigs option and suggested to the other admins that we use > this in order to reduce puppet run times a little.
Thin storeconfigs won't reduce your puppet agent run time, only the master compilation time. > Is it recommended to purge the [mysql] database once the option is > enabled on the puppetmaster? I don't think so. The next run with thin_storeconfigs should get rid of all the extraneous data. > p.s. on another note: I can't grasp the advantage of not using > thin_storeconfigs. Since we'll be parsing the manifests on every change > anyway, having all info replicated into a database doesn't seem to bring > us anything. Is there any use case where not using this option would > make sense? Having all the data in the database can help write inventory applications. If you don't have such application, thin storeconfig is way better. On another hand, if you don't use exported resources/collection, you really don't care about storeconfigs at all and you should disable it altogether. -- 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 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.
