Issue #4302 has been updated by Brice Figureau.
Peter Meier wrote: > Brice and I are observing 2.5 up to 6 times slower compile requests on 2.6 > compared to 0.25.5. > > This ticket is about to document that issue and collecting further > information about it. > > Further investigations: > > As a first thing we need to check, whether only the first compile request is > slower or also subsequent compiles. According to Luke this would indicate > that it is either a parsing or compiling issue. In my case, I'm seeing a 2.5x slower compilation for _all_ run (not only the first one), compared to 0.25.5. I added some benchmark blocks around the various parts of the compilation process to see where we were spending time: 0.25.5 (second compilation of the same node, so no parsing): <pre> info: Expiring the node cache of corp1.daysofwonder.com info: Not using expired node for corp1.daysofwonder.com from cache; expired at Tue Jul 20 19:35:07 +0200 2010 info: Caching node for corp1.daysofwonder.com notice: compiler init in 0.00 seconds notice: Puppet::Parser::Compiler#initvars in 0.00 seconds notice: Puppet::Parser::Compiler#initmain in 0.00 seconds notice: Puppet::Parser::Compiler#node_params in 0.00 seconds notice: Puppet::Parser::Compiler#evaluate_main in 0.02 seconds notice: Puppet::Parser::Compiler#evaluate_ast_node in 1.07 seconds notice: Puppet::Parser::Compiler#evaluate_node_classes in 0.00 seconds notice: Puppet::Parser::Compiler#evaluate_generators in 2.46 seconds notice: Puppet::Parser::Compiler#finish in 0.80 seconds notice: Puppet::Parser::Compiler#fail_on_unevaluated in 0.00 seconds notice: Puppet::Resource::Catalog#to_resouce in 0.93 seconds notice: Compiled catalog for corp1.daysofwonder.com in 5.28 seconds </pre> 2.6.0 (still second compilation): <pre> info: Expiring the node cache of corp1.daysofwonder.com info: Not using expired node for corp1.daysofwonder.com from cache; expired at Tue Jul 20 19:27:45 +0200 2010 info: Caching node for corp1.daysofwonder.com notice: compiler init in 0.00 seconds notice: Puppet::Parser::Compiler#initvars in 0.00 seconds notice: Puppet::Parser::Compiler#set_node_parameters in 0.00 seconds notice: Puppet::Parser::Compiler#create_settings_scope in 0.01 seconds notice: Puppet::Parser::Compiler#evaluate_main in 0.21 seconds notice: Puppet::Parser::Compiler#evaluate_ast_node in 3.84 seconds notice: Puppet::Parser::Compiler#evaluate_node_classes in 0.00 seconds notice: Puppet::Parser::Compiler#evaluate_generators in 4.28 seconds notice: Puppet::Parser::Compiler#finish in 0.21 seconds notice: Puppet::Parser::Compiler#fail_on_unevaluated in 0.00 seconds notice: Puppet::Resource::Catalog#to_resource in 3.62 seconds notice: Compiled catalog for corp1.daysofwonder.com in environment production in 12.19 seconds </pre> So some things to note: * P::R::Catalog#to_resource is now more than 3 times slower * P::P::Compiler#evaluate_ast_node is more than 3 times slower * P::P::Compiler#evaluate_generators is less than 2 times slower I'll dig deeper... ---------------------------------------- Bug #4302: compile performance on 2.6 http://projects.puppetlabs.com/issues/4302 Author: Peter Meier Status: Unreviewed Priority: Normal Assigned to: Category: Target version: Affected version: 2.6.0 Keywords: Branch: Brice and I are observing 2.5 up to 6 times slower compile requests on 2.6 compared to 0.25.5. This ticket is about to document that issue and collecting further information about it. Further investigations: As a first thing we need to check, whether only the first compile request is slower or also subsequent compiles. According to Luke this would indicate that it is either a parsing or compiling issue. Further ideas are welcome. -- 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.
