Puppet

It was reported by Peiter Meier (duritong) that the following manifest:

file {
 "/deep/hierarchy/full/of/files":
   recurse => true, checksum => none, mode => 0600
}

Takes a long time for the first run (when mode is changed).

Analysis of the problem show that we produce many events that are tentatively propagated to the generated file sub-resource, ending in an about O(kn²⁾ performance (with k number of different events, and n number of generated resource). This happens because the transaction masquerades the events source by the topmost file resource. So instead of flowing the events from the real resource we’re trying to flow them from the topmost resource, which is itself linked with out-edges (because of the auto-requiring) to all the sub generated resource.

This is certainly wrong (why would we want to propagate back those events to where they originated?).

The envisioned solution is to filter out all the edges pointing to the generated sub-resources for those events that originate from a linked generated sub-resource.