Issue #14386 has been reported by Deepak Giridharagopal. ---------------------------------------- Feature #14386: Better logging of 'config retrieval' activities https://projects.puppetlabs.com/issues/14386
Author: Deepak Giridharagopal Status: Unreviewed Priority: Normal Assignee: Category: Target version: Affected Puppet version: 2.7.14 Keywords: performance Branch: There is a [thread on this on puppet-dev](https://groups.google.com/forum/?fromgroups#!topic/puppet-dev/VjTmbH0dAAE): Trevor reports: <blockquote> I've noticed an understandable correlation between catalog size and config retrieval time. However, I'm a bit lost as to why it seems so slow. For an example 1.5M catalog: 24 seconds compile time Almost instantaneous transfer time (localhost) 40 seconds registered by the puppet client as the 'Config retrieval time' Why is there almost as much "other stuff" on the client as the original compile time and is there anywhere that I can start looking to potentially optimize it? I'm perfectly willing to accept that it's just doing a lot and that's how long it takes but it seems a bit odd. </blockquote> Without timing information for the various activities that occur during configuration retrieval (downloading plugins, dealing with facts, etc) it's difficult to determine the root cause of any slowdown. Fixing the root cause is obviously the end goal, but some more transparency here would be a good first step. -- 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.
