Issue #14571 has been updated by Ken Barber.
Indeed - any advancement on top of what we have would be good. Breaking down the steps occurring inside each resolution for example. Weither its loading the files (where code still resides), spinning on waiting for dependent resolutions or executing the setcode blocks themselves. For example - I know with the cache patch, I actually clearly say (cached) afterwards ... with --timing switched on. Any information helping the user to understand better where time is spent would be awesome. So +1 to all this. ---------------------------------------- Feature #14571: Add instrumentation to facts https://projects.puppetlabs.com/issues/14571#change-63240 Author: Jeff Weiss Status: Accepted Priority: Normal Assignee: Jeff Weiss Category: testing Target version: 2.X Keywords: Branch: Affected Facter version: As a part of being able to characterize performance of Facter and specific facts, I would love to have instrumentation builtin to Facter (maybe enabled via command option or config file?) that would allow for benchmarking of fact resolution. This can also help us as we persist a cache of resolved facts. -- 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 [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
