Issue #17190 has been updated by eric sorenson.
Hmm... I wonder if some of this is already available in performance instrumentation framework that Brice added in #9584. ---------------------------------------- Feature #17190: detailed accounting/debugging of catalog compilation times https://projects.puppetlabs.com/issues/17190#change-77908 Author: Joshua Hoblitt Status: Needs More Information Priority: Low Assignee: eric sorenson Category: logging Target version: Affected Puppet version: 2.7.19 Keywords: Branch: Recently, something has made my catalog compilation times jump up significantly. All fingers are pointing towards this being the fault of new module(s) that are in use. After some discussion on #puppet, it appears there is no intelligent way of diagnosing the code at fault except by removing modules one at a time from the manifests to see which is at fault. So level of introspection on the catalog build process would be very helpful here. It would be really useful to have a master side debugging mode that would dump detailed timing information on the catalog compilation process into the log. Perhaps something that could be enable for just a single agent names or a wildcard match. I imagine tracing the timing to classes would be difficult but perhaps the amount of time spent on each resource would be possible to account for? Ie, if I knew a ton of time was spent processing sshkey resources I'd could fairly quickly trace that back to the module at fault. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to puppet-bugs@googlegroups.com. To unsubscribe from this group, send email to puppet-bugs+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
