Mailing-List: contact giraph-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: giraph-dev@incubator.apache.org
Date: Tue, 13 Dec 2011 22:29:30 +0000 (UTC)
From: "Claudio Martella (Commented) (JIRA)" <jira@apache.org>
To: giraph-dev@incubator.apache.org
Message-ID: 
 <1964599585.7834.1323815370565.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1672378465.6813.1323803670788.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (GIRAPH-104) Save half of maximum memory used
 from messaging
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Claudio Martella commented on GIRAPH-104:
-----------------------------------------

supposing the messaging pattern doesn't change between superstep 6 and superstep 8 :)

this looks like a great improvement, great work. I went through the review, frankly quite quickly, and it looks very good.

I'll check it out better tomorrow and will +1.
                
> Save half of maximum memory used from messaging
> -----------------------------------------------
>
>                 Key: GIRAPH-104
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-104
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Avery Ching
>            Assignee: Avery Ching
>            Priority: Critical
>         Attachments: GIRAPH-104.diff
>
>
> Currently, the amount of memory that Giraph uses for messaging is huge.  This JIRA will reduce the messaging memory by half and provide periodic updates of memory for debugging.  Details are below:
> Refactored RandomMessageBenchmark to an internal vertex class.  Added aggregators to RandomMessagesBenchmark to track bytes, messages, and time for the messaging.  Adjusted the postSuperstep() to be called after the flush() for more accurate timings.
> Added periodic minute updates for message flushing (which can take a while, especially on the memory benchmark).  This helps to see how progress is going and gives an ETA.
> Memory optimizations include:
> - Clear the message list after computation 
> - Free vertex messages on the source as the flush is going on 
> - TreeMap -> HashMap for VertexMutations
> - Sizing the ArrayList properly in transientInMessages

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira