[
https://issues.apache.org/jira/browse/HAMA-704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571254#comment-13571254
]
Suraj Menon commented on HAMA-704:
----------------------------------
Hi Edward, yes that was one thing which I wanted to suggest, but again, please
don't compare on toString(). WritableComparable extends Writable. This means we
can change V implements WritableComparable. I am afraid, toString().compare is
not a good idea.
{noformat}
((new IntWritable(11)).compare(new IntWritable(2))) != ((new
IntWritable(11)).toString()).compare(new IntWritable(2)).toString())
{noformat}
Also, on performance, let's decide based on data. We need to check how much GC
time did Hama-0.6 release need. And with serialized storage, have we reduced
the same.
Remember right now we are writing and reading message twice on both sender and
receiver side. Once we make it single write on sender side and single read on
receiver side, we should be able to improve numbers there.
> 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: mytest.patch, patch.txt, removeMsgMap.patch
>
>
> <vertex, message> 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
