You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hama.apache.org by "Thomas Jungblut (JIRA)" <ji...@apache.org> on 2011/07/03 18:43:21 UTC

[jira] [Commented] (HAMA-358) Evaluation of Hama BSP communication protocol performance

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

Thomas Jungblut commented on HAMA-358:
--------------------------------------

I asked myself if we need to strictly stick with RPC for BSP Communication.
What about just setting up a SequenceFile and sending it across the network using plain old streams?

We can later add asynchronous communication during computational phases if the SequenceFile reached it's blocksize...

What do you think of it?

> Evaluation of Hama BSP communication protocol performance
> ---------------------------------------------------------
>
>                 Key: HAMA-358
>                 URL: https://issues.apache.org/jira/browse/HAMA-358
>             Project: Hama
>          Issue Type: Improvement
>          Components: bsp, documentation 
>    Affects Versions: 0.3.0
>            Reporter: Edward J. Yoon
>            Assignee: Edward J. Yoon
>             Fix For: 0.4.0
>
>   Original Estimate: 1,008h
>  Remaining Estimate: 1,008h
>
> The goal of this project is performance evaluation of RPC frameworks (e.g., Hadoop RPC, Thrift, Google Protobuf, ..., etc) to figure out which is the best solution for Hama BSP communication. Currently Hama is using Hadoop RPC to communicate and transfer messages between BSP workers.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira