Some thoughts from our similar environment:
1. Puppet client runs are like bugs and a light, they will tend to cluster together. If some client runs are slow, other clients wait, over time, they all end up trying to run at the same time. This was easily observed on the foreman "run distribution over the last 30 minutes" We solved by restarting the client puppet service weekly and using the splay option. 2. Some resources types use more CPU than others, I've observed anything using yum (ensure latest for example) and recursive directories of course. 3. Foreman "report metrics" is a good tool, I just looked at a few of my systems and config_retrieval is about 50% of the ET on the systems sampled. 4. Are modifications happening? Sometimes a class will re-do each puppet run. Those need to be fixed. -- 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.
