On Mon, Apr 25, 2011 at 8:07 AM, <maillists0@gmail.com>
wrote:> Newb question. The style guide contains this:
>
> Inheritance may be used within a module, but must not be used across
> module namespaces. Cross-module dependencies should be satisfied in a
> more portable way that doesn’t violate the concept of modularity, such
> as with include statements or relationship declarations.
>
> That''s self-explanatory and makes perfect sense. Is there also a
> performance cost to inheriting across namespaces?
I presume you mean inheriting a different class in another module.
This would only affect catalog compilation, and not the enforcement of
the catalog and it''s not really measurable in a quick test. You can
check the catalog compile time for comparison. This data should exist
both in summarize option or syslog/store (yaml) report:
$ puppet agent -t --summarize --noop
...
Time:
Config retrieval: 3.11
$ grep retrieval 201104090212.yaml
!ruby/sym config_retrieval: 3.10552787780762
- - config_retrieval
- Config retrieval
Please post additional info if you notice a significant difference.
Thanks,
Nan
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.