You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@giraph.apache.org by "Jakob Homan (Created) (JIRA)" <ji...@apache.org> on 2011/10/15 02:32:11 UTC
[jira] [Created] (GIRAPH-57) Provide PutMsgs RPC call
Provide PutMsgs RPC call
------------------------
Key: GIRAPH-57
URL: https://issues.apache.org/jira/browse/GIRAPH-57
Project: Giraph
Issue Type: Improvement
Reporter: Jakob Homan
Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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
[jira] [Commented] (GIRAPH-57) Add new RPC call
(putVertexIdMessagesList) to batch putMsgList RPCs together
Posted by "Avery Ching (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170857#comment-13170857 ]
Avery Ching commented on GIRAPH-57:
-----------------------------------
Emergency fix to allow trunk to compile on certain platforms:
[ERROR] /home/hudson/hudson-slave/workspace/Giraph-trunk-Commit/trunk/src/main/java/org/apache/giraph/comm/VertexIdMessages.java:[66,45] type parameters of <I>I cannot be determined; no unique maximal instance exists for type variable I with upper bounds I,org.apache.hadoop.io.WritableComparable
==============================================================================
--- incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/VertexIdMessages.java (original)
+++ incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/VertexIdMessages.java Fri Dec 16 09:26:44 2011
@@ -63,7 +63,7 @@ public class VertexIdMessages<I extends
@Override
public void readFields(DataInput input) throws IOException {
- vertexId = BspUtils.createVertexIndex(getConf());
+ vertexId = BspUtils.<I>createVertexIndex(getConf());
> Add new RPC call (putVertexIdMessagesList) to batch putMsgList RPCs together
> ----------------------------------------------------------------------------
>
> Key: GIRAPH-57
> URL: https://issues.apache.org/jira/browse/GIRAPH-57
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
> Assignee: Avery Ching
> Attachments: GIRAPH-57.diff, GIRAPH-57.diff.2
>
>
> Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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
[jira] [Commented] (GIRAPH-57) Add new RPC call
(putVertexIdMessagesList) to batch putMsgList RPCs together
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170586#comment-13170586 ]
Hudson commented on GIRAPH-57:
------------------------------
Integrated in Giraph-trunk-Commit #48 (See [https://builds.apache.org/job/Giraph-trunk-Commit/48/])
GIRAPH-57: Add new RPC call (putVertexIdMessagesList) to batch
putMsgList RPCs together. (aching)
aching : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1214983
Files :
* /incubator/giraph/trunk/CHANGELOG
* /incubator/giraph/trunk/CODE_CONVENTIONS
* /incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/ArrayListWritable.java
* /incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/BasicRPCCommunications.java
* /incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/CommunicationsInterface.java
* /incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/VertexIdMessages.java
* /incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/VertexIdMessagesList.java
* /incubator/giraph/trunk/src/main/java/org/apache/giraph/graph/GiraphJob.java
> Add new RPC call (putVertexIdMessagesList) to batch putMsgList RPCs together
> ----------------------------------------------------------------------------
>
> Key: GIRAPH-57
> URL: https://issues.apache.org/jira/browse/GIRAPH-57
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
> Assignee: Avery Ching
> Attachments: GIRAPH-57.diff
>
>
> Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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
[jira] [Assigned] (GIRAPH-57) Provide PutMsgs RPC call
Posted by "Avery Ching (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Avery Ching reassigned GIRAPH-57:
---------------------------------
Assignee: Avery Ching
> Provide PutMsgs RPC call
> ------------------------
>
> Key: GIRAPH-57
> URL: https://issues.apache.org/jira/browse/GIRAPH-57
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
> Assignee: Avery Ching
>
> Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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
[jira] [Commented] (GIRAPH-57) Provide PutMsgs RPC call
Posted by "Avery Ching (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169147#comment-13169147 ]
Avery Ching commented on GIRAPH-57:
-----------------------------------
Added a new request called putVertexIdMessagesList to reduce the total number of RPCs. Performance has improved a lot. The number of messages per call is configurable with 'giraph.maxMessages\
PerFlushPut'. Here are some examples using RandomMessageBenchmark:
For large messages (10000 bytes) the improvement is decent, here's the old code:
2011-12-13 22:08:01,746 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Outputing statistics for superstep 5
2011-12-13 22:08:01,746 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: superstep total bytes sent : 60000000000
2011-12-13 22:08:01,746 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: total bytes sent : 300000000000
2011-12-13 22:08:01,746 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: superstep total messages : 6000000
2011-12-13 22:08:01,746 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: total messages : 30000000
2011-12-13 22:08:01,746 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: superstep total millis : 928660
2011-12-13 22:08:01,746 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: total millis : 4782825
2011-12-13 22:08:01,746 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: workers : 5
2011-12-13 22:08:01,746 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Superstep megabytes / second = 308.0807775955409
2011-12-13 22:08:01,746 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Total megabytes / second = 299.0934175114864
2011-12-13 22:08:01,746 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Superstep messages / second = 32304.61094480219
2011-12-13 22:08:01,746 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Total messages / second = 31362.21793605244
2011-12-13 22:08:01,746 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Superstep megabytes / second / worker = 61.616155519108176
2011-12-13 22:08:01,746 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Total megabytes / second / worker = 59.818683502297276
2011-12-13 22:08:01,746 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Superstep messages / second / worker = 6460.922188960438
2011-12-13 22:08:01,746 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Total messages / second / worker = 6272.443587210488
And the new code with giraph.maxMessagesPerFlushPut=1000
2011-12-13 21:47:25,873 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Outputing statistics for superstep 5
2011-12-13 21:47:25,873 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: superstep total bytes sent : 60000000000
2011-12-13 21:47:25,873 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: total bytes sent : 300000000000
2011-12-13 21:47:25,873 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: superstep total messages : 6000000
2011-12-13 21:47:25,873 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: total messages : 30000000
2011-12-13 21:47:25,873 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: superstep total millis : 769012
2011-12-13 21:47:25,873 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: total millis : 3816559
2011-12-13 21:47:25,873 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: workers : 5
2011-12-13 21:47:25,873 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Superstep megabytes / second = 372.0387912306635
2011-12-13 21:47:25,873 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Total megabytes / second = 374.8170733399837
2011-12-13 21:47:25,873 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Superstep messages / second = 39011.09475534842
2011-12-13 21:47:25,873 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Total messages / second = 39302.41874945468
2011-12-13 21:47:25,873 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Superstep megabytes / second / worker = 74.4077582461327
2011-12-13 21:47:25,873 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Total megabytes / second / worker = 74.96341466799674
2011-12-13 21:47:25,873 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Superstep messages / second / worker = 7802.218951069684
2011-12-13 21:47:25,873 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Total messages / second / worker = 7860.4837498909355
Performance improvement of (374.8170733399837-299.0934175114864)/299.0934175114864=.2531
About 25% more bytes / second
When the messages are smaller (50 bytes), the effect can be much more dramatic. I think many applications (i.e. PageRank, shortest paths, etc.) will have smaller messages and actually see this effect.
Old code:
2011-12-13 22:17:39,232 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Outputing statistics for superstep 5
2011-12-13 22:17:39,232 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: superstep total bytes sent : 600000000
2011-12-13 22:17:39,232 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: total bytes sent : 3000000000
2011-12-13 22:17:39,232 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: superstep total messages : 12000000
2011-12-13 22:17:39,232 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: total messages : 60000000
2011-12-13 22:17:39,232 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: superstep total millis : 280977
2011-12-13 22:17:39,232 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: total millis : 1456479
2011-12-13 22:17:39,232 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: workers : 5
2011-12-13 22:17:39,232 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Superstep megabytes / second = 10.182409767414237
2011-12-13 22:17:39,232 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Total megabytes / second = 9.821710265711864
2011-12-13 22:17:39,232 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Superstep messages / second = 213540.61008552302
2011-12-13 22:17:39,232 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Total messages / second = 205976.19327158167
2011-12-13 22:17:39,232 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Superstep megabytes / second / worker = 2.0364819534828476
2011-12-13 22:17:39,232 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Total megabytes / second / worker = 1.964342053142373
2011-12-13 22:17:39,233 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Superstep messages / second / worker = 42708.1220171046
2011-12-13 22:17:39,233 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Total messages / second / worker = 41195.23865431633
New code with giraph.maxMessagesPerFlushPut=5000
2011-12-13 22:37:43,610 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Outputing statistics for superstep 5
2011-12-13 22:37:43,610 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: superstep total bytes sent : 600000000
2011-12-13 22:37:43,610 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: total bytes sent : 3000000000
2011-12-13 22:37:43,610 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: superstep total messages : 12000000
2011-12-13 22:37:43,610 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: total messages : 60000000
2011-12-13 22:37:43,610 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: superstep total millis : 23975
2011-12-13 22:37:43,611 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: total millis : 123956
2011-12-13 22:37:43,611 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: workers : 5
2011-12-13 22:37:43,611 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Superstep megabytes / second = 119.33359537930136
2011-12-13 22:37:43,611 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Total megabytes / second = 115.40477868028776
2011-12-13 22:37:43,611 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Superstep messages / second = 2502606.882168926
2011-12-13 22:37:43,611 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Total messages / second = 2420213.6241892283
2011-12-13 22:37:43,611 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Superstep megabytes / second / worker = 23.86671907586027
2011-12-13 22:37:43,611 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Total megabytes / second / worker = 23.080955736057554
2011-12-13 22:37:43,611 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Superstep messages / second / worker = 500521.3764337852
2011-12-13 22:37:43,611 INFO org.apache.giraph.benchmark.RandomMessageBenchmark$RandomMessageBenchmarkWorkerContext: Total messages / second / worker = 484042.72483784566
Performance improvement of about (115.40477868028776-9.821710265711864)/9.821710265711864=10.7499
About 1075% more bytes / second
> Provide PutMsgs RPC call
> ------------------------
>
> Key: GIRAPH-57
> URL: https://issues.apache.org/jira/browse/GIRAPH-57
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
> Assignee: Avery Ching
>
> Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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
[jira] [Resolved] (GIRAPH-57) Add new RPC call
(putVertexIdMessagesList) to batch putMsgList RPCs together
Posted by "Avery Ching (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Avery Ching resolved GIRAPH-57.
-------------------------------
Resolution: Fixed
Thanks Claudio! I just want to note that I added the Apache License header to VertexIdMessages.java before committing. Duh!
> Add new RPC call (putVertexIdMessagesList) to batch putMsgList RPCs together
> ----------------------------------------------------------------------------
>
> Key: GIRAPH-57
> URL: https://issues.apache.org/jira/browse/GIRAPH-57
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
> Assignee: Avery Ching
> Attachments: GIRAPH-57.diff
>
>
> Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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
[jira] [Commented] (GIRAPH-57) Add new RPC call
(putVertexIdMessagesList) to batch putMsgList RPCs together
Posted by "Jakob Homan (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170605#comment-13170605 ]
Jakob Homan commented on GIRAPH-57:
-----------------------------------
Can we post the final patch, along with the "I give this to Apache" button?
> Add new RPC call (putVertexIdMessagesList) to batch putMsgList RPCs together
> ----------------------------------------------------------------------------
>
> Key: GIRAPH-57
> URL: https://issues.apache.org/jira/browse/GIRAPH-57
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
> Assignee: Avery Ching
> Attachments: GIRAPH-57.diff
>
>
> Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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
[jira] [Updated] (GIRAPH-57) Add new RPC call
(putVertexIdMessagesList) to batch putMsgList RPCs together
Posted by "Avery Ching (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Avery Ching updated GIRAPH-57:
------------------------------
Summary: Add new RPC call (putVertexIdMessagesList) to batch putMsgList RPCs together (was: Provide PutMsgs RPC call)
> Add new RPC call (putVertexIdMessagesList) to batch putMsgList RPCs together
> ----------------------------------------------------------------------------
>
> Key: GIRAPH-57
> URL: https://issues.apache.org/jira/browse/GIRAPH-57
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
> Assignee: Avery Ching
>
> Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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
[jira] [Commented] (GIRAPH-57) Add new RPC call
(putVertexIdMessagesList) to batch putMsgList RPCs together
Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170859#comment-13170859 ]
Hudson commented on GIRAPH-57:
------------------------------
Integrated in Giraph-trunk-Commit #49 (See [https://builds.apache.org/job/Giraph-trunk-Commit/49/])
Ancillary to GIRAPH-57 (type parameters of <I>I cannot be determined).
aching : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1215070
Files :
* /incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/VertexIdMessages.java
> Add new RPC call (putVertexIdMessagesList) to batch putMsgList RPCs together
> ----------------------------------------------------------------------------
>
> Key: GIRAPH-57
> URL: https://issues.apache.org/jira/browse/GIRAPH-57
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
> Assignee: Avery Ching
> Attachments: GIRAPH-57.diff, GIRAPH-57.diff.2
>
>
> Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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
[jira] [Commented] (GIRAPH-57) Add new RPC call
(putVertexIdMessagesList) to batch putMsgList RPCs together
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169630#comment-13169630 ]
jiraposter@reviews.apache.org commented on GIRAPH-57:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3201/
-----------------------------------------------------------
(Updated 2011-12-14 19:50:29.358317)
Review request for giraph.
Changes
-------
Forgot a few important files (VertexIdMessages.java and VertexIdMessagesList.java)
Summary
-------
Added new putVertexIdMessagesList RPC and supporting classes (VertexIdMessages and VertexIdMessagesList) to reduce the total number of RPCs during a flush. This improves the number of RPC / sec and overall I/O bandwidth. The amount of batching is done by the total number of messages and is configurable at runtime (default of 5000, weighted toward helping smaller messages). I have noted some performance results in https://issues.apache.org/jira/browse/GIRAPH-57 (between 25 - 1075 percent improvements).
Also, while tinkering with BasicRPCCommunications, notices inconsistent spaces between 'synchronized' and '('. Removed spaces and standardized in the CODE_CONVENTIONS.
This addresses bug GIRAPH-57.
https://issues.apache.org/jira/browse/GIRAPH-57
Diffs (updated)
-----
http://svn.apache.org/repos/asf/incubator/giraph/trunk/CODE_CONVENTIONS 1213849
http://svn.apache.org/repos/asf/incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/ArrayListWritable.java 1213849
http://svn.apache.org/repos/asf/incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/BasicRPCCommunications.java 1214406
http://svn.apache.org/repos/asf/incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/CommunicationsInterface.java 1213849
http://svn.apache.org/repos/asf/incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/VertexIdMessages.java PRE-CREATION
http://svn.apache.org/repos/asf/incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/VertexIdMessagesList.java PRE-CREATION
http://svn.apache.org/repos/asf/incubator/giraph/trunk/src/main/java/org/apache/giraph/graph/GiraphJob.java 1213849
Diff: https://reviews.apache.org/r/3201/diff
Testing
-------
Passed local and Hadoop unittests. Used the RandomMessageBenchmark on a small cluster.
Thanks,
Avery
> Add new RPC call (putVertexIdMessagesList) to batch putMsgList RPCs together
> ----------------------------------------------------------------------------
>
> Key: GIRAPH-57
> URL: https://issues.apache.org/jira/browse/GIRAPH-57
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
> Assignee: Avery Ching
> Attachments: GIRAPH-57.diff
>
>
> Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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
[jira] [Updated] (GIRAPH-57) Add new RPC call
(putVertexIdMessagesList) to batch putMsgList RPCs together
Posted by "Avery Ching (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Avery Ching updated GIRAPH-57:
------------------------------
Attachment: GIRAPH-57.diff.2
With the final patch (+Apache license header on VertexIdMessages.java).
> Add new RPC call (putVertexIdMessagesList) to batch putMsgList RPCs together
> ----------------------------------------------------------------------------
>
> Key: GIRAPH-57
> URL: https://issues.apache.org/jira/browse/GIRAPH-57
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
> Assignee: Avery Ching
> Attachments: GIRAPH-57.diff, GIRAPH-57.diff.2
>
>
> Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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
[jira] [Commented] (GIRAPH-57) Provide PutMsgs RPC call
Posted by "Avery Ching (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128005#comment-13128005 ]
Avery Ching commented on GIRAPH-57:
-----------------------------------
I think that the actual RPCs are done in bulk so that combining can take effect on the client side. Actually, I believe in our current code Hyunsik changed this to flush at the every end until the maximum vertices is reached.
> Provide PutMsgs RPC call
> ------------------------
>
> Key: GIRAPH-57
> URL: https://issues.apache.org/jira/browse/GIRAPH-57
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
>
> Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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
[jira] [Commented] (GIRAPH-57) Add new RPC call
(putVertexIdMessagesList) to batch putMsgList RPCs together
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170532#comment-13170532 ]
jiraposter@reviews.apache.org commented on GIRAPH-57:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3201/#review3928
-----------------------------------------------------------
Ship it!
Looks cool and straight from here. All those CODE_CONVENTIONS fixes made it looks scary from far.
- Claudio
On 2011-12-14 19:50:29, Avery Ching wrote:
bq.
bq. -----------------------------------------------------------
bq. This is an automatically generated e-mail. To reply, visit:
bq. https://reviews.apache.org/r/3201/
bq. -----------------------------------------------------------
bq.
bq. (Updated 2011-12-14 19:50:29)
bq.
bq.
bq. Review request for giraph.
bq.
bq.
bq. Summary
bq. -------
bq.
bq. Added new putVertexIdMessagesList RPC and supporting classes (VertexIdMessages and VertexIdMessagesList) to reduce the total number of RPCs during a flush. This improves the number of RPC / sec and overall I/O bandwidth. The amount of batching is done by the total number of messages and is configurable at runtime (default of 5000, weighted toward helping smaller messages). I have noted some performance results in https://issues.apache.org/jira/browse/GIRAPH-57 (between 25 - 1075 percent improvements).
bq.
bq. Also, while tinkering with BasicRPCCommunications, notices inconsistent spaces between 'synchronized' and '('. Removed spaces and standardized in the CODE_CONVENTIONS.
bq.
bq.
bq. This addresses bug GIRAPH-57.
bq. https://issues.apache.org/jira/browse/GIRAPH-57
bq.
bq.
bq. Diffs
bq. -----
bq.
bq. http://svn.apache.org/repos/asf/incubator/giraph/trunk/CODE_CONVENTIONS 1213849
bq. http://svn.apache.org/repos/asf/incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/ArrayListWritable.java 1213849
bq. http://svn.apache.org/repos/asf/incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/BasicRPCCommunications.java 1214406
bq. http://svn.apache.org/repos/asf/incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/CommunicationsInterface.java 1213849
bq. http://svn.apache.org/repos/asf/incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/VertexIdMessages.java PRE-CREATION
bq. http://svn.apache.org/repos/asf/incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/VertexIdMessagesList.java PRE-CREATION
bq. http://svn.apache.org/repos/asf/incubator/giraph/trunk/src/main/java/org/apache/giraph/graph/GiraphJob.java 1213849
bq.
bq. Diff: https://reviews.apache.org/r/3201/diff
bq.
bq.
bq. Testing
bq. -------
bq.
bq. Passed local and Hadoop unittests. Used the RandomMessageBenchmark on a small cluster.
bq.
bq.
bq. Thanks,
bq.
bq. Avery
bq.
bq.
> Add new RPC call (putVertexIdMessagesList) to batch putMsgList RPCs together
> ----------------------------------------------------------------------------
>
> Key: GIRAPH-57
> URL: https://issues.apache.org/jira/browse/GIRAPH-57
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
> Assignee: Avery Ching
> Attachments: GIRAPH-57.diff
>
>
> Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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
[jira] [Updated] (GIRAPH-57) Add new RPC call
(putVertexIdMessagesList) to batch putMsgList RPCs together
Posted by "Avery Ching (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Avery Ching updated GIRAPH-57:
------------------------------
Attachment: GIRAPH-57.diff
Same as the reviewboard (https://reviews.apache.org/r/3201/)
> Add new RPC call (putVertexIdMessagesList) to batch putMsgList RPCs together
> ----------------------------------------------------------------------------
>
> Key: GIRAPH-57
> URL: https://issues.apache.org/jira/browse/GIRAPH-57
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
> Assignee: Avery Ching
> Attachments: GIRAPH-57.diff
>
>
> Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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
[jira] [Commented] (GIRAPH-57) Add new RPC call
(putVertexIdMessagesList) to batch putMsgList RPCs together
Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169627#comment-13169627 ]
jiraposter@reviews.apache.org commented on GIRAPH-57:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/3201/
-----------------------------------------------------------
Review request for giraph.
Summary
-------
Added new putVertexIdMessagesList RPC and supporting classes (VertexIdMessages and VertexIdMessagesList) to reduce the total number of RPCs during a flush. This improves the number of RPC / sec and overall I/O bandwidth. The amount of batching is done by the total number of messages and is configurable at runtime (default of 5000, weighted toward helping smaller messages). I have noted some performance results in https://issues.apache.org/jira/browse/GIRAPH-57 (between 25 - 1075 percent improvements).
Also, while tinkering with BasicRPCCommunications, notices inconsistent spaces between 'synchronized' and '('. Removed spaces and standardized in the CODE_CONVENTIONS.
This addresses bug GIRAPH-57.
https://issues.apache.org/jira/browse/GIRAPH-57
Diffs
-----
http://svn.apache.org/repos/asf/incubator/giraph/trunk/CODE_CONVENTIONS 1213849
http://svn.apache.org/repos/asf/incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/ArrayListWritable.java 1213849
http://svn.apache.org/repos/asf/incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/BasicRPCCommunications.java 1214406
http://svn.apache.org/repos/asf/incubator/giraph/trunk/src/main/java/org/apache/giraph/comm/CommunicationsInterface.java 1213849
http://svn.apache.org/repos/asf/incubator/giraph/trunk/src/main/java/org/apache/giraph/graph/GiraphJob.java 1213849
Diff: https://reviews.apache.org/r/3201/diff
Testing
-------
Passed local and Hadoop unittests. Used the RandomMessageBenchmark on a small cluster.
Thanks,
Avery
> Add new RPC call (putVertexIdMessagesList) to batch putMsgList RPCs together
> ----------------------------------------------------------------------------
>
> Key: GIRAPH-57
> URL: https://issues.apache.org/jira/browse/GIRAPH-57
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
> Assignee: Avery Ching
>
> Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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
[jira] [Commented] (GIRAPH-57) Add new RPC call
(putVertexIdMessagesList) to batch putMsgList RPCs together
Posted by "Avery Ching (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170602#comment-13170602 ]
Avery Ching commented on GIRAPH-57:
-----------------------------------
I only ran mvn package =(. I need to remember to do mvn install next time. Sorry.
> Add new RPC call (putVertexIdMessagesList) to batch putMsgList RPCs together
> ----------------------------------------------------------------------------
>
> Key: GIRAPH-57
> URL: https://issues.apache.org/jira/browse/GIRAPH-57
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
> Assignee: Avery Ching
> Attachments: GIRAPH-57.diff
>
>
> Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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
[jira] [Commented] (GIRAPH-57) Provide PutMsgs RPC call
Posted by "Jakob Homan (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13128007#comment-13128007 ]
Jakob Homan commented on GIRAPH-57:
-----------------------------------
Using a combiner will consolidate multiple messages to a single vertex, but what I'm suggesting is to (essentially) combine multiple putMsg calls to all the vertices on a worker (after combining). It may be best just to build this into individual RPC mechanisms, although the current RPCCommunications class knows more about when all the messages to a particular vertex have been {{putMsg}}ed than do the individual proxies.
> Provide PutMsgs RPC call
> ------------------------
>
> Key: GIRAPH-57
> URL: https://issues.apache.org/jira/browse/GIRAPH-57
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
>
> Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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
[jira] [Commented] (GIRAPH-57) Add new RPC call
(putVertexIdMessagesList) to batch putMsgList RPCs together
Posted by "Claudio Martella (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170601#comment-13170601 ]
Claudio Martella commented on GIRAPH-57:
----------------------------------------
I guess how it passed mvn install...
> Add new RPC call (putVertexIdMessagesList) to batch putMsgList RPCs together
> ----------------------------------------------------------------------------
>
> Key: GIRAPH-57
> URL: https://issues.apache.org/jira/browse/GIRAPH-57
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
> Assignee: Avery Ching
> Attachments: GIRAPH-57.diff
>
>
> Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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
[jira] [Commented] (GIRAPH-57) Provide PutMsgs RPC call
Posted by "Avery Ching (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169093#comment-13169093 ]
Avery Ching commented on GIRAPH-57:
-----------------------------------
I've been working on this one and it's a big improvement. I will dump the code after GIRAPH-104 is committed.
> Provide PutMsgs RPC call
> ------------------------
>
> Key: GIRAPH-57
> URL: https://issues.apache.org/jira/browse/GIRAPH-57
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
> Assignee: Avery Ching
>
> Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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
[jira] [Commented] (GIRAPH-57) Add new RPC call
(putVertexIdMessagesList) to batch putMsgList RPCs together
Posted by "Avery Ching (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13170489#comment-13170489 ]
Avery Ching commented on GIRAPH-57:
-----------------------------------
Anyone wanna review? This is a pretty straightforward change with obvious improvements in performance...
> Add new RPC call (putVertexIdMessagesList) to batch putMsgList RPCs together
> ----------------------------------------------------------------------------
>
> Key: GIRAPH-57
> URL: https://issues.apache.org/jira/browse/GIRAPH-57
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
> Assignee: Avery Ching
> Attachments: GIRAPH-57.diff
>
>
> Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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
[jira] [Closed] (GIRAPH-57) Add new RPC call
(putVertexIdMessagesList) to batch putMsgList RPCs together
Posted by "Avery Ching (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GIRAPH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Avery Ching closed GIRAPH-57.
-----------------------------
Sorry about the error guys.
> Add new RPC call (putVertexIdMessagesList) to batch putMsgList RPCs together
> ----------------------------------------------------------------------------
>
> Key: GIRAPH-57
> URL: https://issues.apache.org/jira/browse/GIRAPH-57
> Project: Giraph
> Issue Type: Improvement
> Reporter: Jakob Homan
> Assignee: Avery Ching
> Attachments: GIRAPH-57.diff, GIRAPH-57.diff.2
>
>
> Right now messages are sent to a vertex one at a time. It would be good to have a putMsgs call that could send messages to multiple vertices (all hosted on the same worker). We'd save a huge number of individual RPC calls at the expense of having smaller calls with larger payloads.
--
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