[
https://issues.apache.org/jira/browse/GIRAPH-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486204#comment-13486204
]
Eli Reisman commented on GIRAPH-389:
------------------------------------
Are we talking about mutliple threads per-worker trying to claim splits?
because that will really really slow ZK down.
I assumed the worker had an executor service, claimed splits, and passed the
split reading job off to a thread after each claim (znode write) is successful.
The fewer actors out there contending for splits on the ZK list, the happier ZK
will be because each claim attempt involves a ZK write attempt.
Regarding this patch: do I need to do anything else or now that jenkins is
happy, we're all set on this commit?
Thanks!
> 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
