[
https://issues.apache.org/jira/browse/GIRAPH-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259841#comment-13259841
]
Avery Ching commented on GIRAPH-185:
------------------------------------
Since we only allocate one ConcurrentHashMap per worker, the empty overhead
isn't a concern. If however, the per element memory cost of a entry into the
concurrent hash map is much more expensive then I would definitely be worried.
We can also tune the concurrency level (default 16) to a reasonable tradeoff.
> Improve concurrency of putMsg / putMsgList
> ------------------------------------------
>
> Key: GIRAPH-185
> URL: https://issues.apache.org/jira/browse/GIRAPH-185
> Project: Giraph
> Issue Type: Improvement
> Components: graph
> Affects Versions: 0.2.0
> Reporter: Bo Wang
> Assignee: Bo Wang
> Fix For: 0.2.0
>
> Attachments: GIRAPH-185.patch
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Currently in putMsg / putMsgList, a synchronized closure is used to protect
> the whole transientInMessages when adding the new message. This lock prevents
> other concurrent calls to putMsg/putMsgList and increases the response time.
> We should use fine-grain locks to allow high concurrency in message
> communication.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
