Return-Path: X-Original-To: apmail-hama-dev-archive@www.apache.org Delivered-To: apmail-hama-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D592D10213 for ; Mon, 9 Sep 2013 15:12:08 +0000 (UTC) Received: (qmail 74451 invoked by uid 500); 9 Sep 2013 15:12:08 -0000 Delivered-To: apmail-hama-dev-archive@hama.apache.org Received: (qmail 74336 invoked by uid 500); 9 Sep 2013 15:12:07 -0000 Mailing-List: contact dev-help@hama.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hama.apache.org Delivered-To: mailing list dev@hama.apache.org Received: (qmail 74327 invoked by uid 99); 9 Sep 2013 15:12:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Sep 2013 15:12:06 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of clin4j@googlemail.com designates 209.85.160.46 as permitted sender) Received: from [209.85.160.46] (HELO mail-pb0-f46.google.com) (209.85.160.46) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Sep 2013 15:12:02 +0000 Received: by mail-pb0-f46.google.com with SMTP id rq2so6230917pbb.19 for ; Mon, 09 Sep 2013 08:11:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=mfbJ0cZZfcG6iZUznXdDj5KLgwwAFYMlaOdZupg/Yb0=; b=RyCSPKZtqhYkVVGOMYbxhTjcB0S8knp8IL+hg0gc09sbSSrXLYnwcQsJaIRePEskLV NvXd+dEq8Gy1dR2UKzcSBEbDe98gFgrHpfO4omH0etcJbEJ/+BVh7wCXQnJrlu73rfuq AcuFVyXWojAcZEpbX1D23LSsHCu8B6AEWNpXO3r/maJMooGv4eOyxSMaKd3co3vFvbwU 1ih+RhglYwTne0vB3bDuadU1NuG8yQ08pI7mJf1WK9fU5Pbo+OQvbgZc4NAEEIA/bKv7 LtXIJv5nBcxQ+3tK8X6SF8FBUGJo18ElN0k+swVG4JxzPu2hJ1/JmObiOngVQKGcwtoW fK0A== MIME-Version: 1.0 X-Received: by 10.68.24.199 with SMTP id w7mr2201973pbf.202.1378739502233; Mon, 09 Sep 2013 08:11:42 -0700 (PDT) Received: by 10.70.102.163 with HTTP; Mon, 9 Sep 2013 08:11:42 -0700 (PDT) In-Reply-To: References: Date: Mon, 9 Sep 2013 23:11:42 +0800 Message-ID: Subject: Re: [DISCUSS] Hama 0.7.0 From: Chia-Hung Lin To: dev@hama.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org That looks fine to me. In addition to this, if that task is accomplished, are we planning to release a new version (e.g. a minor version plus 1)? Just to check as it seems that we have demands on frequent releases so that users who need some specific patches can use it earlier. On 3 September 2013 09:45, Edward J. Yoon wrote: > According to Suraj's dependency diagram, asynchronous messaging is > most important and highest priority for us at the moment. How about we > focus on this one? (Of course, some committers can dedicated on doing > GPU, ML algorithms, or Interface Refactoring issues, regardless of > *core* roadmap). > > If we agree with this plan, I think we can separate the async > messaging into smaller sub-tasks: > > * Decision of whether we will use existing open source, or not. > * Design the asynchronous messaging interface (maybe (spilling) > message queue also should be considered together?). > * Implementation of asynchronous messaging functions, such as send or flush. > * Evaluation and adopt asynchronous messaging as a default messenger system. > > WDYT? > > > On Mon, Sep 2, 2013 at 11:31 PM, Chia-Hung Lin wrote: >> +1 >> >> BTW, are we going to prioritize tasks in roadmap? >> >> >> >> >> On 28 August 2013 14:17, Tommaso Teofili wrote: >>> sure, it looks reasonable to me. >>> Tommaso >>> >>> >>> >>> 2013/8/28 Edward J. Yoon >>> >>>> Hi all, >>>> >>>> After we release the 0.6.3 (HDFS 2.0 version), we have to work for 0.7.0 >>>> version now. >>>> >>>> I would like to suggest that we solve the messaging scalability issue. >>>> WDYT? >>>> >>>> ... >>>> >>>> And, according to my experiments, BSP framework shows very nice performance >>>> (I tested also GraphLab and Spark). Only Graph job is slow. So, I'll mainly >>>> work on improving the performance of GraphJobRunner. >>>> >>>> -- >>>> Best Regards, Edward J. Yoon >>>> @eddieyoon >>>> > > > > -- > Best Regards, Edward J. Yoon > @eddieyoon