[
https://issues.apache.org/jira/browse/HAMA-511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205300#comment-13205300
]
Thomas Jungblut commented on HAMA-511:
--------------------------------------
I see this a bit more important than you.
Currently GoldenOrb has folded, so our only "competitor" is Giraph.
Giraph is focused on Graph computing solely with the "simple" BSP case.
Suraj is right, we should support a flexible engine for every execution kind.
We can cover the simple case with the normal BSP and Pregel-api as well, but
can be much wider usable.
An interesting point is as well, that this system equals to Dryad.
Dryad has been dropped by Microsoft in favor of Hadoop and we can bring it back
on top of Hadoop.
We should just ask ourselfs, why they dropped dryad.
I wouldn't make this a submodule, anyways this would be a greater change
throughout the whole code base. But afterwards our system is much more powerful
than it is now.
bq. BTW, I'm reading Valiant's BSP and MS's dryad papers and just wondered why
these jobs should running in timeshared-fashion on a cluster. If we schedules
job based on resource sharing architecture like Hadoop, it may be possible. But
what's the disadvantages?
I believe it has performance reasons. Timesharing looks like a more ancient
scheduling to me.
> Submitting heterogenous supersteps with precedence constraints on Hama
> ----------------------------------------------------------------------
>
> Key: HAMA-511
> URL: https://issues.apache.org/jira/browse/HAMA-511
> Project: Hama
> Issue Type: New Feature
> Reporter: Suraj Menon
> Priority: Minor
> Attachments: Defining supersteps for BSP.pdf
>
>
> Hama should support submission of jobs with support for:
> 1) Skipping unwanted superstep synchronization.
> 2) Run supersteps with heterogenous nature of computation
> 3) Scheduling supersteps with precedence constraints.
> An explanation of these is provided in the attachment.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
