On 22/03/11 19:08, Jennings, Jared L CTR USAF AFMC 46 SK/CCI wrote: > I've got somewhere around 130 Augeas resources in my policy (catalog, > entire set of manifests, what-have-you) and 11 custom lenses, each for > only one or two files, and it takes like 2 1/2 minutes to apply the > whole thing. Looking at the --debug output, there are a whole lot of > pauses right after "opening Augeas" sorts of lines. (That happens 79 > times.) I think that's because Augeas is populating its whole tree, each > time. > > I know I can avoid that behavior by specifying the lens and incl > parameters in my augeas resources, but I like the clarity I get by not > doing that, and want to preserve it. > > Has anyone ever tried to make it so that only one Augeas connection is > opened per Puppet run?
I saw your suggestion here and filed it a little while back: https://projects.puppetlabs.com/issues/6920 More recently at Puppet Camp I realised there's a slightly better way of optimising the loading, which I've tried to implement in this issue: https://projects.puppetlabs.com/issues/7285 If you get the chance to test it, I'd appreciate any feedback via the issue report. I suspect the method's a bit fragile, so testing's needed. There's also a change that Mike Knox has been working on, which will halve the time taken by Puppet when an Augeas resource has to be applied. It's under the guise of showing file diffs for Augeas actions, but happily speeds it up too: https://projects.puppetlabs.com/issues/2728 Hopefully this focus on Puppet+Augeas performance will help out your catalog runs in the future! Cheers, -- Dominic Cleal Red Hat Consulting m: +44 (0)7818 512168 -- 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.
