Selective synchronization can be much cleaner if you treat this as a graph of supersteps.
2012/2/10 Edward J. Yoon <[email protected]> > There's a trade off I think. Simple/agile/easy-to-use vs. complex job > optimization. > > If both barrier and selective sync types can coexist in a hama-core, I'm > +1. > > If there's some plan to implement acyclic graph job manager, it'd be nice > if we create new module I think. > > 나의 iPhone에서 보냄 > > 2012. 2. 10. 오후 6:05 "Thomas Jungblut (Commented) (JIRA)" <[email protected]> > 작성: > > > We should just ask ourselfs, why they dropped dryad. > -- Thomas Jungblut Berlin <[email protected]>
