On Thu, May 3, 2012 at 2:25 PM, Trevor Vaughan <[email protected]>wrote:
> All, > > 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. > Whether or not the 'config retrieval time' is unavoidable, this certainly seems like a part of the agent/master flow that could use some more transparency. If we logged the time spent for various parts of config retrieval, would that help at least triangulate the problem? I've created https://projects.puppetlabs.com/issues/14386 to track this. deepak -- Deepak Giridharagopal / Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en.
