On Wed, 2013-02-20 at 10:11 +0100, David Schmitt wrote: > Hi, > > meditating over a 13 minute runtime of an agent who's managing 4200 > resources, I found this: > > -rw-rw---- 1 root root 1.8M Feb 20 09:45 > /var/lib/puppet/state/state.yaml > > I seem to remember that yaml serialization can be a problem. Is there a > way to use json for the state.yaml or should I file a bug on that? > > > > Here's the catalog, already in json, so that seems to work out: > > -rw-rw---- 1 root root 6.4M Feb 20 10:06 > /var/lib/puppet/client_data/catalog/fqdn.example.com.json
You didn't mention the version of puppet you used (but I believe it's already the 3.x). Can you run with --summarize so that we have a look to where the time is spent (do you manage sloooow resources)? I'd be suprised if you're spending most of the time in saving the client state, but that would be interesting to check. -- Brice Figureau Follow the latest Puppet Community evolutions on www.planetpuppet.org! -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
