You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@giraph.apache.org by "Craig Muchinsky (JIRA)" <ji...@apache.org> on 2014/08/01 13:56:38 UTC

[jira] [Commented] (GIRAPH-927) Decouple netty server threads from message processing

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

Craig Muchinsky commented on GIRAPH-927:
----------------------------------------

I was able to verify that the async.patch corrected the task shutdown issue.

> Decouple netty server threads from message processing
> -----------------------------------------------------
>
>                 Key: GIRAPH-927
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-927
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Sergey Edunov
>         Attachments: GIRAPH-927.patch, async.patch
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> Our profiling shows that a lot of apps are neither CPU nor memory or network bound. Instead they waste a lot of time waiting for lock in MessageStore. That happens in netty threads. 
> We should be able to put messages into queue and then process them in other set of threads. 
> It has to be configurable because adding another thread level will introduce additional overhead. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)