[
https://issues.apache.org/jira/browse/HAMA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13021542#comment-13021542
]
Thomas Jungblut commented on HAMA-380:
--------------------------------------
The order is not the problem, the problem was to support multiple messages in a
bundle.
No one actually should write the size and vertices and then expect to come
elements in that ordering. We just should support this, because this was
actually working before the patch. There are plenty of situations where this
could be useful, but my example wasn't well picked ;)
Never the less I agree with your design POV!
Nice work! +1
> Send messages in batches to reduce RPC overhead.
> ------------------------------------------------
>
> Key: HAMA-380
> URL: https://issues.apache.org/jira/browse/HAMA-380
> Project: Hama
> Issue Type: Improvement
> Components: bsp
> Affects Versions: 0.3.0
> Reporter: Miklos Erdelyi
> Assignee: Miklos Erdelyi
> Fix For: 0.3.0
>
> Attachments: HAMA-380-v2.patch, bspmsgbundle.patch,
> bspmsgbundle.v2.patch
>
> Original Estimate: 4h
> Remaining Estimate: 4h
>
> When profiling graph computations running on HAMA it turned out that huge
> amount of time is spent in RPC calls.
> To reduce this overhead I propose extending the GroomServer's API with a
> put(BSPMessageBundle) method so that a group of messages can be transferred
> from the caller to the callee at once. Also, the sync() operation should be
> improved by sending messages in batches rather than one-by-one.
> Using BSPMessageBundle makes it easier to add support for compression of
> messages later.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
