Issue #4302 has been updated by Brice Figureau.

Markus Roberts wrote:
> I'm going to be tied up / on an odd(er) schedule the rest of the week, but 
> I'm planning on doing some delving into anything you turn up whenever I can 
> carve out the time.  I'll prioritize looking for algorithmic improvements to 
> any areas you can isolate as being suspiciously slow, and post partial fixes 
> as I come up with them.

Upon a closer examination of the two last hotspots, it seems that now code 
evaluation takes longer than it took in 0.25. Since this only change I can 
remind in this area (besides the large refactoring) is that more things are now 
in TypeCollection. I suspect we either are doing more work than before in the 
TypeCollection or that some of the inner operations are now taking longer.

My next step will be to rupy-prof to_resource in both version and compare the 
outcome. This one looks easier to find the real issue.
----------------------------------------
Bug #4302: compile performance on 2.6
http://projects.puppetlabs.com/issues/4302

Author: Peter Meier
Status: Accepted
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.

Reply via email to