W dniu czwartek, 29 listopada 2012 18:23:23 UTC+1 użytkownik Jeff McCune napisał: > > It might not be the cause, but one related change we made in Puppet 3 is > that we scan Ruby gem's and will load extensions contained within them. > This is #7788 [1] This change in behavior could be causing the Puppet > autoloader to perform a _lot_ of additional stat() system calls. Could you > run strace, truss, or dtrace and compare the number of system calls between > Puppet 2.7 and 3.0 in your environment?
not sure if it's about 2.7 => 3.0 migration, as we did it month ago with no aparent degradation (but also no such load decrease as on some slides from PC). now we just switched to newer ruby and passenger (1.8.7 => 1.9.3p327 and 3.0.2 => 3.0.17). i'll try to do some tests tomorrow but i need to get both instances up at the same server. another thing that is involved (and suspected) is hiera, as compilation time deltas differ on different groups of nodes, and it might be related to how much of modules with hiera lookups are included on mostly affected nodes (ie. 120s => 240s on our load balancers). another thing is puppetdb, but nodes that collect resources, which should impose highest load on puppetdb are not the ones which are much affected (ie. 320s => 360s increase on our nagios server). is it possible to do evaltrace on puppetmaster? -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/ShLDKg4XRUkJ. 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.
