On Wed, 7 Dec 2016 at 14:54 Trevor Vaughan <[email protected]> wrote:
> I was looking through the puppetlabs-concat module as well as some of my > modules that have aggregation functionality and I realized that the catalog > really shouldn't be sending the intermediary resources to the client. > > While I'm not positive, the ability to mark resources as ephemeral *might* > go a long way toward solving the 10k+ resources issue. > > The idea is that only the final 'aggregation' resource would be present in > the catalog and all other resources would be removed right after they are > processed. > > The main issue that I see with this is in debugging. However, I think this > is pretty much the case with concat presently so I don't know that it > changes much. > > Thoughts? > Another issue would be resource relationships on ephemeral resources. They might not be that common on concat_fragment, but on anchor it is pretty common to use them. Also I think some benchmarking how much they actually slow down things would be good. And checking if there is anything that can be optimized when applying resources that do nothing. /Erik -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/CAAAzDLfUzXQ-ZxzhZF2xT3bPFpLUbGMKaX%2BGnWAVvFurkGqs7A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
