The bottom line is that I don't have an explanation for why your compilations are so slow. Sorry. I don't think it's anything specific to defined types, except inasmuch as defined type instances do have overhead comparable to that of native type instances. Perhaps the guys over on puppet-dev would have a suggestion about how you can profile catalog compilation to get an idea of where all the time is spent.
On Monday, January 28, 2013 10:04:51 AM UTC-6, asq wrote: > > i know that those times are high. but anyway i can't find a single "bit" > that makes it so. i think puppet is very sensitible to the way its used. > when you look at ruby 1.8/1.9 comparisions for the same manifests, you can > clearly see that something worrying is happening, as newer ruby should be > more optimized, but instead it runs significantly slower. > > Of course Puppet's compilation speed is sensitive to the contents of your manifests, and more so than just to their raw size. It may be that you can substantially improve your performance if you can identify the problem area(s). On the other hand, I don't think it's at all safe to assume that a higher-version Ruby (or anything else) should yield greater performance. Performance optimization is certainly one development objective, but it is often at odds with new feature implementation and even with bug fixes. Especially with between Ruby 1.8 and Ruby 1.9 there are some deep changes in Ruby's string handling and character I/O, and these (among other things) might easily exact a performance penalty from applications, such as Puppet, that do a lot of text manipulation. John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.