Issue #17190 has been updated by Joshua Hoblitt.
Hmm - thinking about it some more, I don't think the profiling process
necessarily needs to be bound to the master. Something like this would be
really useful:
puppet catalog compile --trace ...
Re: Master side, what about allowing the agent to request a compilation trace
for the the current run only? That would avoid having to eat the log volume /
overhead of tracing all runs and would fit nicely into my typically debugging
work flow. If wishes were unicorns, I'd want to be able to request the tracing
from the agent and have the agent print the results to the standard out.
Perhaps like:
puppet agent --test --compiletrace
----------------------------------------
Feature #17190: detailed accounting/debugging of catalog compilation times
https://projects.puppetlabs.com/issues/17190#change-77906
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 [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.
