[
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
