giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Avery Ching (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-389) Multithreading should intelligently allocate the thread pools
Date Mon, 29 Oct 2012 18:02:12 GMT

    [ https://issues.apache.org/jira/browse/GIRAPH-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486210#comment-13486210
] 

Avery Ching commented on GIRAPH-389:
------------------------------------

Yes, multiple threads per worker are claiming splits.  But as you mentioned before the split
list is read once and passed to all the input split threads.  Each one will then only read
the zknodes to claim the split.

No, you don't need to do anything, Jenkins is happy.  Thanks again.
                
> 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

Mime
View raw message