[
https://issues.apache.org/jira/browse/GIRAPH-927?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14068479#comment-14068479
]
Craig Muchinsky commented on GIRAPH-927:
----------------------------------------
I tried out this new feature but noticed that when I set the async message
thread count > 0 my map tasks are not shutting down, I was forced to manually
kill them off after the job was complete. Has anybody else seen this behavior?
> 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
>
> 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)
