Return-Path: X-Original-To: apmail-incubator-hama-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-hama-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 73E0E4006 for ; Sun, 3 Jul 2011 16:43:47 +0000 (UTC) Received: (qmail 78578 invoked by uid 500); 3 Jul 2011 16:43:47 -0000 Delivered-To: apmail-incubator-hama-dev-archive@incubator.apache.org Received: (qmail 78476 invoked by uid 500); 3 Jul 2011 16:43:46 -0000 Mailing-List: contact hama-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hama-dev@incubator.apache.org Delivered-To: mailing list hama-dev@incubator.apache.org Received: (qmail 78468 invoked by uid 99); 3 Jul 2011 16:43:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 Jul 2011 16:43:46 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 03 Jul 2011 16:43:43 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id E3AD1443384 for ; Sun, 3 Jul 2011 16:43:21 +0000 (UTC) Date: Sun, 3 Jul 2011 16:43:21 +0000 (UTC) From: "Thomas Jungblut (JIRA)" To: hama-dev@incubator.apache.org Message-ID: <712954437.880.1309711401929.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1608487277.650.1299492779372.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HAMA-358) Evaluation of Hama BSP communication protocol performance MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ 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