> I'm cross-posting this to both the users and dev groups so that the
> users can use the workaround technique to reduce graph churn and the
> devs can hopefully fix the issue.
> 
> So, I'm loving stages, but they appear, by default, to generate a
> many-to-many dependency graph.
> 
> By adding 'pre' and 'post' stages that contain a single item, the graphs
> are vastly reduced in complexity and we're seeing something like a 3X
> speedup in graph execution in simple test cases.
> 
> I've attached a couple of puppet files illustrating the issue with their
> associated graphs.

Sweet.  Thank you.

> If the graphs could be auto-reduced to a single point prior to execution
> automatically, it would be quite helpful.

So we had explored this idea (via a dummy resource called a whit) but
apparently dropped the ball (probably me...IIRC I had way too many balls
at that point).

-- Markus

-- 
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.

Reply via email to