Best option from my side would be to cache the locations of the binaries per puppet run probably best would be to do it while the providers are initialized and then hopefully this method is not being called at all.
Ohad On Tue, Oct 13, 2009 at 4:10 PM, Brice Figureau < [email protected]> wrote: > > On Tue, 2009-10-13 at 09:27 +0800, Ohad Levy wrote: > > Why don't we cache the binary location? we end up querying per each > > rpm package where is yum where is rpm and where is python. > > Because things can change between a run or subsequent runs.o > Imagine your provider requires an executable that is not yet installed, > but during a run it gets installed. We need to find it on the next run. > > > in my original setup, i had approx 1300 packages, each one triggered 3 > > x which ~ 0.07 second times 1300 = 90 seconds > > > > it seems a trivial fix to add a hash lookup instead of searching the > > path each time. > > Sure, but then we need a way to invalidate the hash... > -- > Brice Figureau > Follow the latest Puppet Community evolutions on www.planetpuppet.org! > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Developers" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
