Mailing-List: contact dev-help@hama.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hama.apache.org
Date: Mon, 3 Feb 2014 06:32:09 +0000 (UTC)
From: "Edward J. Yoon (JIRA)" <jira@apache.org>
To: dev@hama.apache.org
Message-ID: <JIRA.12688674.1389672662514.25795.1391409129370@arcas>
In-Reply-To: <JIRA.12688674.1389672662514@arcas>
References: <JIRA.12688674.1389672662514@arcas>
Subject: [jira] [Updated] (HAMA-849) No need to use sorted queue for
 outgoingQueue
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HAMA-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Edward J. Yoon updated HAMA-849:
--------------------------------

    Status: In Progress  (was: Patch Available)

Patch applied.

> No need to use sorted queue for outgoingQueue 
> ----------------------------------------------
>
>                 Key: HAMA-849
>                 URL: https://issues.apache.org/jira/browse/HAMA-849
>             Project: Hama
>          Issue Type: Improvement
>          Components: bsp core, graph
>    Affects Versions: 0.6.3
>            Reporter: Edward J. Yoon
>            Assignee: Edward J. Yoon
>             Fix For: 0.7.0
>
>         Attachments: HAMA-849.patch
>
>
> Basically message transfer protocol provides senderQueue and receiverQueue separately. Since only incoming queue should be sorted, there's no need to use sorted queue for outgoingQueue.
> In graphJobRunner case, we can use diskqueue and sortedqueue to reduce the memory usage until sorted spilling queue is implemented.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)