On Thursday, July 12, 2012 3:29:15 AM UTC-5, badamowicz wrote: > > I started doing some experiments with the configuration option > 'thin_storeconfigs=true' by adding this option to one of my Puppet masters. > However, I could not determine any change in behavior. I expected to have > the resources collected faster, but Puppet still takes some 15min to do the > job. So maybe I misunderstood something. Should this option instead be > placed in the client's configuration to make them export only the > @@-resources? > > Couldn't find any documentation. So any help is appreciated. > > Google gave me this as my number one hit: http://projects.puppetlabs.com/projects/1/wiki/Using_Stored_Configuration. It's a bit dated, but it nevertheless contains the key information: "[thin storeconfigs] only collects and stores to the database exported resources, tags and host facts."
'Thick' storeconfigs additionally stores non-exported resources, and possibly other things -- overall, a relational representation of nodes' entire catalogs. I would expect thin storeconfigs to accelerate resource collection relative to thick only if the *overall* database size were slowing the DBMS. If the problem is specifically with the number and/or complexity of exported resources, then thin vs. thick should not make a difference in that area. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/ehNmEJw6uVUJ. 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.
