[ https://issues.apache.org/jira/browse/GIRAPH-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259859#comment-13259859 ]
Avery Ching commented on GIRAPH-185: ------------------------------------ About the sent messages, it is the superstep sent messages =). Therefore if you are looking at the last superstep, there are 0 sent messages. If the supersteps are long enough, you will see this number change per superstep. Pre-population is certainly appears to be a tradeoff of memory vs performance. Can you run a few experiments to justify the 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