giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claudio Martella (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-504) Create ComputeContext
Date Wed, 06 Feb 2013 15:53:13 GMT

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

Claudio Martella commented on GIRAPH-504:
-----------------------------------------

It would be nice if concurrency was transparent (read: if the users kept on ignoring that
computation is concurrent). That is why Pregel was designed at first place. If I have to start
thinking about concurrency and such, I'd better go to my own MPI-based stuff which buys me
1000x performance. Ok, maybe we can leave the *Context classes to the "power user". As we
cannot ensure that implementations are synchronized, there is not much we could do (and it
probably would kill performance if we could).
                
> Create ComputeContext
> ---------------------
>
>                 Key: GIRAPH-504
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-504
>             Project: Giraph
>          Issue Type: New Feature
>            Reporter: Maja Kabiljo
>            Assignee: Maja Kabiljo
>         Attachments: GIRAPH-504.diff
>
>
> Right now we have WorkerContext which is accessible from vertex.compute, but it's not
thread safe - usually if we want to use it with multithreaded computation we have to use synchronization.
Instead we can create a ComputeContext, which is going to have one instance per compute thread.

--
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