Notice: Finished catalog run in 486.54 seconds
Changes:
Events:
Resources:
Total: 2304
Time:
Filebucket: 0.00
Apt key: 0.00
Anchor: 0.00
Schedule: 0.00
Group: 0.00
Exec: 0.00
User: 0.00
Ssh authorized key: 0.00
Package: 0.39
Last run: 1440488641
Service: 2.71
Config retrieval: 2.91
File: 22.60
Total: 28.62
Version:
Config: 1440488048
Puppet: 3.8.1
The summarized view looks good but it seems puppet spends a lot of time in different other places that don't count for the summarize.
1. Debug: Loaded state in 119.18 seconds
2. Debug: Loaded state in 156.15 seconds
3. Debug: Stored state in 252.81 seconds
What is causing those excessive times for Loading and Storing the state. I did not really find a lot of hints on that topic.
Due to some ideas i already changed most of my recurse options for file type to recurse => "remote"
I also found the hint to use checksum => "none" but not sure about the effect of that change.
Any hints are welcome
Regards
Constantin
2015-08-26 14:48:21 +0000 Puppet (debug): Storing state
2015-08-26 14:55:23 +0000 Puppet (debug): Stored state in 422.03 seconds
What I'm interested in is how i can improve performance of that step.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/05bacd31-8a6c-4ab5-bdd3-a323f12ff249%40googlegroups.com.--
You received this message because you are subscribed to a topic in the Google Groups "Puppet Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/BzfsN9axWss/unsubscribe.
To unsubscribe from this group and all its topics, send an email to puppet-users...@googlegroups.com.
> 5. mailto:puppet-users+unsub...@googlegroups.com
> 8. mailto:puppet-users+unsub...@googlegroups.com