Still, 4~7s is ages in processing time. I am sure you can
serialize/unserialize several MBs of stuff in that time, and catalogs
are usually tiny...
cheers,
m
On Mon, Jun 3, 2013 at 12:33 PM, Eric Sorenson
wrote:
> On Jun 3, 2013, at 12:44 AM, christian.le.fl...@gmail.com wrote:
>
> Reason I'
On Jun 3, 2013, at 12:44 AM, christian.le.fl...@gmail.com wrote:
> Reason I'm asking: catalog compiling for this agent takes 3 to 4 sec tops. So
> there are still 4 to 7 sec in which other things must happen then.
Yes: serialization, transmission over the network, deserialization.
The master
Reason I'm asking: catalog compiling for this agent takes 3 to 4 sec tops.
So there are still 4 to 7 sec in which other things must happen then.
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiv
Thanks, didn't know catalog compiling on the master has its share in the
"config retrieval" statistic for the client... makes sense. BTW: is there a
list of things somewhere that are done during "config retrieval"?
--
You received this message because you are subscribed to the Google Groups
"P
On May 24, 2013, at 7:33 AM, christian.le.fl...@gmail.com wrote:
> So catalog caching takes less than 2 sec. but there's something else
> indicated by three lines starting with "###" that takes up a big part of the
> 11 sec. Can you tell me what this is or how I can find it out?
At that time
I'll try that, thanks.
Am 24.05.2013 21:00 schrieb "Dustin J. Mitchell" :
> Does strace help to figure that out?
>
> Dustin
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> To unsubscribe from this group and stop receiving emails fro
Does strace help to figure that out?
Dustin
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubscr...@googlegroups.com.
To post to this group,
Hi,
while trying to find things in our puppet setup I could tune I had a look
into /var/lib/puppet/state/last_run_summary.yaml and saw the time consumed
by "config_retrieval" which is always around 11 sec.
> cat /var/lib/puppet/state/last_run_summary.yaml
---
resources:
total: 983
sch
