Just to elaborate more, there is a tradeoff:
 - fresh changes should be propagated as fast as possible in the "opening move" to bootstrap into the fast second phase
 - if changes happen in bursts, it is more efficient to wait and aggregate multiple changes

In this PR the algorithm in its current shape is very sensitive to batching and might cause storms downstream because of its deterministic spread -- so I expect it to not work in this form. I want to test it though, to see how it actually behaves, even if it is wrong.