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 73EFD4D92 for ; Thu, 19 May 2011 08:15:31 +0000 (UTC) Received: (qmail 54764 invoked by uid 500); 19 May 2011 08:15:31 -0000 Delivered-To: apmail-incubator-hama-dev-archive@incubator.apache.org Received: (qmail 54748 invoked by uid 500); 19 May 2011 08:15:31 -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 54740 invoked by uid 99); 19 May 2011 08:15:30 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 May 2011 08:15:30 +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; Thu, 19 May 2011 08:15:27 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 4EB84D0804 for ; Thu, 19 May 2011 08:14:47 +0000 (UTC) Date: Thu, 19 May 2011 08:14:47 +0000 (UTC) From: "Thomas Jungblut (JIRA)" To: hama-dev@incubator.apache.org Message-ID: <2143125511.26031.1305792887304.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1094136074.652.1299492899376.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Issue Comment Edited] (HAMA-359) Development of Shortest Path Finding Algorithm 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-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035423#comment-13035423 ] Thomas Jungblut edited comment on HAMA-359 at 5/19/11 8:13 AM: --------------------------------------------------------------- Obviously the task gets executed in a seperate VM. Sorry for that wrong stuff ;D I'm tracking the GC problem now. The task itself is fine, it just consumes 700mb. To profile the others we need to add this line to hama/hama: {noformat} HAMA_OPTS="$HAMA_OPTS -agentpath:/usr/local/yk/libyjpagent.so" {noformat} SuperStep 15: Each groom has 50mb allocated and arround 300k integermessages in ram. At this point there is no problem ;D Okay so I've seen the problem during superstep 23, a whole lot of messages are coming in and there wasn't enough heap to fit in causing the whole process to get a big GC pause. Sadly I coudn't get any snapshots because the profiler crashed. was (Author: thomas.jungblut): Obviously the task gets executed in a seperate VM. Sorry for that wrong stuff ;D I'm tracking the GC problem now. The task itself is fine, it just consumes 700mb. To profile the others we need to add this line to hama/hama: {noformat} HAMA_OPTS="$HAMA_OPTS -agentpath:/usr/local/yk/libyjpagent.so" {noformat} SuperStep 15: Each groom has 50mb allocated and arround 300k integermessages in ram. At this point there is no problem ;D > Development of Shortest Path Finding Algorithm > ---------------------------------------------- > > Key: HAMA-359 > URL: https://issues.apache.org/jira/browse/HAMA-359 > Project: Hama > Issue Type: New Feature > Components: examples > Affects Versions: 0.2.0 > Reporter: Edward J. Yoon > Assignee: Thomas Jungblut > Labels: gsoc, gsoc2011, mentor > Fix For: 0.3.0 > > Attachments: HAMA-359-v2.patch, HAMA-359-v3.patch, HAMA-359-v4.patch, HAMA-359.patch, eddie.patch > > Original Estimate: 2016h > Remaining Estimate: 2016h > > The goal of this project is development of parallel algorithm for finding a Shortest Path using Hama BSP. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira