Issue #4803 has been updated by Nikolay Sturm.
With the development version of cucumber-puppet (clone master from github, rake build install), you can do this: $ cd puppet $ cucumber-puppet-gen world and then use this feature: Feature: Performancetest Scenario: one Given a node specified by "node1.yaml" When I compile its catalog Then compilation should succeed And all resource dependencies should resolve Scenario: two Given a node specified by "node2.yaml" When I compile its catalog Then compilation should succeed And all resource dependencies should resolve ... You can add a couple more scenarios to make the effect more clear. Running this feature with puppet 0.25.5 and 2.6.X should show significant performance differences. I hope this is clear enough, let me know if it isn't. cheers, Nikolay ---------------------------------------- Bug #4803: Performance degradation with cucumber-puppet http://projects.puppetlabs.com/issues/4803 Author: Nikolay Sturm Status: Needs more information Priority: Normal Assignee: Category: Target version: Affected version: 2.6.1 Keywords: Branch: Since Puppet 2.6.0, running a test suite with cucumber-puppet takes much longer than with 0.25.5. It seems, Puppet::Node::Environment#known_resource_types calls perform_initial_import each time a catalog is compiled, whereas the old code would only import files once for the whole test suite. For an initial discussion of the issue, see "possible performance degradation with puppet 2.6" on puppet-dev@ -- 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.
