Issue #12310 has been updated by R.I. Pienaar.
Pluginsync or no pluginsync does not make a performance difference. Infact is seems pluginsync is just always on. Without enabling pluginsync it still picks up the facts in the modules anyway and I dont see a diff in speed, additionally in apply mode pluginsync doesnt actually copy the plugins to $libdir, and this is a significant shortcoming. Something to note between 2.7.9 and .10 is: 2.7.9: <pre> # envpuppet work/puppet/bin/puppet apply --modulepath=/etc/puppet/manifests/common/modules /etc/puppet/manifests/site.pp --verbose info: Loading facts in puppet_enabled info: Loading facts in etc_facts_loader info: Loading facts in devco_kvm info: Applying configuration version '1328009162' </pre> 2.7.10: <pre> # envpuppet work/puppet/bin/puppet apply --modulepath=/etc/puppet/manifests/common/modules /etc/puppet/manifests/site.pp --verbose info: Loading facts in /etc/puppet/manifests/common/modules/puppet/lib/facter/puppet_enabled.rb info: Loading facts in /etc/puppet/manifests/common/modules/puppet/lib/facter/etc_facts_loader.rb info: Loading facts in /etc/puppet/manifests/common/modules/puppet/lib/facter/devco_kvm.rb info: Loading facts in /etc/puppet/manifests/common/modules/puppet/lib/facter/puppet_enabled.rb info: Loading facts in /etc/puppet/manifests/common/modules/puppet/lib/facter/etc_facts_loader.rb info: Loading facts in /etc/puppet/manifests/common/modules/puppet/lib/facter/devco_kvm.rb info: Applying configuration version '1328009297' </pre> Which lines up with what I said on IRC last night - it's back to loading facts twice a run. I am running every merge commit between 2.7.9 and 2.7.10 now and gathering timings, will update once I have that ---------------------------------------- Bug #12310: Significant slow down in 2.7.10 apply https://projects.puppetlabs.com/issues/12310 Author: R.I. Pienaar Status: Investigating Priority: Normal Assignee: Category: Target version: Affected Puppet version: Keywords: Branch: I've been exploring approaches for running puppet masterless and in the same time trying to massage my manifests to be compatible with 2.7.x scoping etc. I noticed a huge increase in run times between 2.6.9 and 2.7.10 with the same manifests, using envpuppet and a git clone I've gathered this information: <pre> ======== 2.6.9 notice: Finished catalog run in 9.95 seconds envpuppet puppet apply --pluginsync 14.45s user 4.99s system 92% cpu 21.098 total ======== 2.7.9 notice: Finished catalog run in 16.52 seconds envpuppet puppet apply --pluginsync 21.92s user 6.90s system 93% cpu 30.814 total ======== 2.7.10 notice: Finished catalog run in 21.34 seconds envpuppet puppet apply --pluginsync 23.58s user 9.42s system 73% cpu 44.662 total </pre> 2.7.0 to 2.7.9 performs the same. While 2.7.0-9 is already a fair bit slower than 2.6 was 2.7.10 adds another 14 seconds to the run using the same manifests on the same machine. Comparing last_run_summary.yaml files I notice that the big change in run time info is service: <pre> 2.6.9: service: 2.920294 2.7.9: service: 8.238562 2.7.10: service: 12.400952 </pre> But this does not on it's own account for the time increase there seems to be a hit somewhere like state.yaml handling or report handling or something that isn't reflected here. Unsure how to gather more useful information to narrow this down -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
