On 07/01/11 20:44, Jeff McCune wrote: > -Jeff > > On Jan 7, 2011, at 6:51 AM, Brice Figureau > <brice-pup...@daysofwonder.com> wrote: > >> On Fri, 2011-01-07 at 15:33 +0100, Sébastien Barthélémy wrote: >>> Hello again, >>> >>> thank you for your answers. I use puppet 2.6.4. >>> I don't think I have a site.pp >>> >>> On Wed, 5 Jan 2011, Patrick wrote: >>>> I'm finding that with my version of puppet (2.6.4), the checksum line >>> has no effect on the run time when run on a directory containing 10 files >>> that total 7.5GB. I am not >>>> using the source parameter and it takes just over 2 seconds to run with >>> "checksum => none" or "checksum => md5". My test computer is a Core 2 Duo >>> running on a laptop. I am >>>> not using a puppetmaster to test. >>>> I'm still interested to see if adding that line helps though. >>> >>> I think the line does not help. >>> >>> Here are subsequent calls to puppet. >>> The 3 first runs are with the line, the last line without. >>> >>> The first call is really long because it had work to do >>> (perms to fix), the subsequents were no-ops. >>> >>> $ sudo time puppet -l /tmp/puppet.log ~/puppet/respeer.pp >>> 38779.74 real 38230.77 user 153.85 sys >>> $ sudo time puppet -l /tmp/puppet.log ~/puppet/respeer.pp >>> 388.47 real 380.06 user 4.00 sys >>> $ sudo time puppet -l /tmp/puppet.log ~/puppet/respeer.pp >>> 398.06 real 390.21 user 4.08 sys >>> $ sudo time puppet -l /tmp/puppet.log ~/puppet/respeer.pp >>> 385.04 real 376.70 user 4.00 sys >> >> It would be interesting to try with 0.25.5 (and still use checksum => >> none), to compare times and see if we have a regression or not. > > I think checksumming is a red herring. > >> How many files do you have in total? > > This is the primary issue think. Puppet models all of the files and > Directories as resources and adds dependency relationships among them. > It then sorts the graph. I suspect the sorting of the resource graph > is your performance issue here.
To my knowledge the sub-child resources are spawned during the transaction evaluation so even though they're part of the graph they're never really sorted (the sort phase happens before). But you're right the graph becomes deep and large, which consumes memory. What might happen is what happened pre 0.25.5: too many events are generated (at least one for every file change) and propagated to all the other nodes (ie a n square problem). -- 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-us...@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.
