On Fri, Jul 8, 2011 at 3:00 PM, Haitao Jiang <jianghai...@gmail.com> wrote:

> I just wondering if anyone can point me to the documentation on the
> metric section of a report. I have a slow agent run which has
> following numbers:
>
> Config Retrieval        10.43 seconds
> Exec    0.00 seconds
> File    157.11 seconds
> Filebucket      0.00 seconds
> Package         0.07 seconds
> Schedule        0.00 seconds
> Total   167.62 seconds
>
> I would like to know meaning of above in order to find out the reasons
> of slowness. My guess is it was due to the network latency, but just
> want to make sure.
>

It's telling you that it only took 10 seconds to talk to the server and
retrieve the catalog, and almost all your time was spent in File resources.

File resources impose a different kind of load upon the server, as when they
have a remote source the client needs to request file metadata in order to
compare locally and determine whether or not the file contents need to be
retrieved from the server.

If you have lots of File resources, multiple concurrent clients, and are
still running with the webrick Puppet master, you'll see performance
degradation like this.

If you have deep recursive directories in a File resource, you'll run into
similar issues.

If you have very large files, the default checksumming will take a while.

There are a few parameters that are designed to help with these cases.

http://docs.puppetlabs.com/references/stable/type.html#file

Have a look at recurse and checksum.


-- 
Nigel Kersten
Product Manager, Puppet Labs
Twitter: @nigelkersten

*Join us for **PuppetConf *<http://www.bit.ly/puppetconfsig>
September 22nd and 23rd in Portland, Oregon, USA.
*
*

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en.

Reply via email to