On 20/03/10 17:51, Peter Meier wrote: >>> It was still hanging for about 30s after reporting to have finished >>> the transaction and still burning cpu, but this is rather negligible >>> concerning the amount of time it wasted before and this might also >>> not be related to that issue. >> >> >> We're actually getting to the point where recursive file management is >> reasonable to do on large file sets. Not quite, but we're a heckuva >> lot closer. Wish we'd known earlier what a barrier this (relatively >> simple, in the end) problem was to efficiency. > > btw: ohad mentioned that puppet might be calculating the yaml for the > report while still burning cpu. This might actually be the case. However > 1) does puppet standalone actually do any reports? b) if yes, looks like > it can't be turned off with --report false
I think it does the transaction cleanup which involves removing from the graph all the generated resources. Granted it has no use in puppet, but not puppetd. -- Brice Figureau My Blog: http://www.masterzen.fr/ -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to puppet-...@googlegroups.com. To unsubscribe from this group, send email to puppet-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
