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 62CECEE49 for ; Fri, 15 Feb 2013 13:05:16 +0000 (UTC) Received: (qmail 47479 invoked by uid 500); 15 Feb 2013 13:05:15 -0000 Delivered-To: apmail-hama-dev-archive@hama.apache.org Received: (qmail 47233 invoked by uid 500); 15 Feb 2013 13:05:15 -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 46461 invoked by uid 99); 15 Feb 2013 13:05:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Feb 2013 13:05:14 +0000 Date: Fri, 15 Feb 2013 13:05:14 +0000 (UTC) From: "Suraj Menon (JIRA)" To: dev@hama.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HAMA-704) Optimization of memory usage during message processing MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HAMA-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13579152#comment-13579152 ] Suraj Menon commented on HAMA-704: ---------------------------------- Yes! Sorting would take more time, especially till messaging is synchronous. I am not an expert, but can we call compute before aggregation by master? As we decided, you can check this on the new branch. On a side note, have you profiled and checked the number of objects created in the process? Every compare in SortedQueue involves creating new String object. Can you check if removing and doing VertexId.compare(otherVertexId) makes any difference. I would suggest that the requirements get defined here. The design should get things to work on 16GB 400 node cluster as well as a 4GB 15 node cluster. In any scenario, if we reach the main memory limit, we would have to spill to disk or find some other modes of persistence. > Optimization of memory usage during message processing > ------------------------------------------------------ > > Key: HAMA-704 > URL: https://issues.apache.org/jira/browse/HAMA-704 > Project: Hama > Issue Type: Improvement > Components: graph > Reporter: Edward J. Yoon > Assignee: Edward J. Yoon > Priority: Critical > Fix For: 0.6.1 > > Attachments: hama-704_v05.patch, localdisk.patch, mytest.patch, patch.txt, patch.txt, removeMsgMap.patch > > > map seems consume a lot of memory. We should figure out an efficient way to reduce memory. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira