[
https://issues.apache.org/jira/browse/GIRAPH-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486161#comment-13486161
]
Avery Ching commented on GIRAPH-389:
------------------------------------
Thanks Eli for the review.
We already read splits in parallel with multithreading, but this ensures that
not all the inputs go to the same worker when mulithreading is turned on.
This also deals with the compute threads only spinning up enough threads to
cover the number of partitions they have, no more.
> Multithreading should intelligently allocate the thread pools
> -------------------------------------------------------------
>
> Key: GIRAPH-389
> URL: https://issues.apache.org/jira/browse/GIRAPH-389
> Project: Giraph
> Issue Type: Bug
> Reporter: Avery Ching
> Assignee: Avery Ching
> Fix For: 0.2.0
>
> Attachments: GIRAPH-389.patch
>
>
> Even if the user suggests a very high number of threads, the input split
> threads should not exceed the number splits divided by the number of workers.
> The number of compute threads should not be greater than the number of
> partitions on that worker.
--
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
