Issue #2272 has been updated by Luke Kanies.

Status changed from Accepted to Ready for Testing
Assigned to changed from Luke Kanies to James Turnbull

Added to my repo in the tickets/master/2272 branch, and mailed to the list.

Caching will always be an iterative problem - we'll need to constantly be on 
the lookout for areas that could use caching.  As mentioned in the mail to the 
list, there are still some obvious places to look, but this commit series 
should be enough to give others ideas on how to add caching for their own 
testing.
----------------------------------------
Refactor #2272: Modulepath and autoload information should be cached
http://projects.reductivelabs.com/issues/2272

Author: Luke Kanies
Status: Ready for Testing
Priority: Normal
Assigned to: James Turnbull
Category: plumbing
Target version: 0.25.0
Affected version: 0.24.8


Nigel Kersten has discovered that essentially ridiculous amounts of time are 
being spent searching through modules for plugins.  After simple analysis, the 
following problems (all relatively easily solved with caching) were found:

* Every instance of a defined resource created during compiling results in a 
complete search through the module path
* Every search through the module path results in checking every module for 
plugins, every time

I think there were a couple other smaller issues.

The Puppet::Util::Cacher module should be extended a bit to make caching this 
information for brief period of time (e.g., the filetimeout, which is 15 
seconds) easy, and then it should be used in all of these places to cache this 
information.

Initial testing showed some of this caching can result in an immediate 30% 
reduction in compile time, in some cases.


-- 
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://reductivelabs.com/redmine/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