hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Jungblut (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HAMA-569) Make Hama scalable as more processing is done
Date Thu, 12 Jul 2012 14:28:34 GMT

    [ https://issues.apache.org/jira/browse/HAMA-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13412833#comment-13412833
] 

Thomas Jungblut commented on HAMA-569:
--------------------------------------

We can use the parallel sliding window technology so not all tasks need to run in parallel.


https://code.google.com/p/graphchi/wiki/IntroductionToGraphChi

The idea is really smart, we should incorperate this idea into our framework.

                
> Make Hama scalable as more processing is done
> ---------------------------------------------
>
>                 Key: HAMA-569
>                 URL: https://issues.apache.org/jira/browse/HAMA-569
>             Project: Hama
>          Issue Type: Improvement
>          Components: bsp core
>    Affects Versions: 0.4.0, 0.5.0
>            Reporter: praveen sripati
>             Fix For: 0.6.0
>
>
> Currently Hama doesn't scale. Once the job has been submitted, the # of the bsp tasks
is fixed. So, there are fixed costs associated with the job. The JIRA is to evaluate if Hama
can be made scalable automatically once the job has been submitted and provide a solution
for the same. This applies to both batch and real time processing.
> For ex., in the case of real time processing the # of bsp tasks once the job has been
submitted remain the same for 1 or a million inputs per second.

--
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

        

Mime
View raw message