Issue #4302 has been updated by Luke Kanies.
You are entirely correct. I figured it was this kind of issue - I added a bunch of machinery, and there's too much magic in some of it, which results in unnecessary calls being made. How does performance change if you just remove this call at an appropriate point? (I know that breaks some functionality, but it'd be a useful test.) My naïve guess is that we should basically just call this at the start of a compile and never again. This might have some threadedness issues or something, but in general it should at least reduce it so we never get more than one call per client. ---------------------------------------- Bug #4302: compile performance on 2.6 http://projects.puppetlabs.com/issues/4302 Author: Peter Meier Status: Accepted Priority: High 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.
