Actually, I don't think that these really provide a distributed memory layer.
What they is multiple iterations without having to renegotiate JVM launches, local memory that persists across iterations and decent message passing. (and of course some level of synchronization). And that is plenty for us. On Fri, Sep 16, 2011 at 12:14 AM, Jake Mannix <[email protected]> wrote: > A big "distributed memory layer" does indeed sound great, however. Spark > and Giraph both provide their own, although the former seems to lean more > toward "read-only, with allowed side-effects", and very general purpose, > while the latter is couched in the language of graphs, and computation is > specifically BSP (currently), but allows for fairly arbitrary mutation (and > persisting final results back to HDFS). >
