On Thursday, October 30, 2014 11:56:14 PM UTC-4, Garrett Honeycutt wrote: > > Hi Georgi, > > The catalog compilation time is how long it takes to compile the catalog > *on the master*. You can find it on CentOS with `grep Compile > /var/log/messages`. The amount of time it takes for your agent to run is > not at all tied with how long it takes to compile the catalog. Your > puppet agents are not talking to the puppet master once they have > received the catalog, except for file requests[1] and to submit a report. > The catalog compile on ruby 1.8.7 was about 12-14 seconds. On 2.1.4 it is now about 7-8. In either case we should be well within our limit (I came up with about ~5400 nodes for 2.1.4 and ~3300 on 1.8.7 from your formula above).
> If you are solving for long agent runs, check out the logs which include > timing information. My issue was that requests in queue in the passenger-watch output was hitting the max and client runs would just start timing out. Actually, sometime last night something happened and puppet stopped processing requests altogether. Stopping and starting httpd fixed this, but this could be just some bug in one of the new versions of software I upgraded to. I'll keep monitoring. > By chance are you serving any large binary files with Puppet? > No, all we're serving is some autofs maps and about a dozen tiny config files. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e67c1dc2-b6b8-4934-b1fe-8d8110eed800%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
