The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Feature #14386

Better logging of 'config retrieval' activities

Added by Deepak Giridharagopal almost 2 years ago. Updated almost 2 years ago.

Status:AcceptedStart date:05/09/2012
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:3.x
Affected Puppet version:2.7.14 Branch:
Keywords:performance

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket may be automatically exported to the PUP project on JIRA using the button below:


Description

There is a thread on this on puppet-dev:

Trevor reports:

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.

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.

History

#1 Updated by Andrew Parker almost 2 years ago

  • Status changed from Unreviewed to Accepted
  • Target version set to 3.x

Also available in: Atom PDF