[
https://issues.apache.org/jira/browse/GIRAPH-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486151#comment-13486151
]
Eli Reisman commented on GIRAPH-388:
------------------------------------
Yeah I orginally did the worker addressing this way and was asked to change it
to workerInfo -> PartitionId -> vertId + Collection<M> maps to preserve the
partitionId so that its already provided on the receiver side. I think Avery's
idea was its too expensive or slow to recalc each vertexId -> partitionId
mapping while deserializing incoming message bundles at the receiver. I think
the comments are on the 328 thread.
> Improve the way we keep outgoing messages
> -----------------------------------------
>
> Key: GIRAPH-388
> URL: https://issues.apache.org/jira/browse/GIRAPH-388
> Project: Giraph
> Issue Type: Improvement
> Reporter: Maja Kabiljo
> Attachments: GIRAPH-388.patch
>
>
> As per discussion on GIRAPH-357, in standard application chances that we get
> to use client-side combiner are very low. I experimented with benefits which
> we can get from not having the client-side combiner at all. It turns out that
> having a lot of maps in SendMessageCache, and then collection inside each of
> them, really hurts the performance.
--
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
