[jira] [Updated] (GIRAPH-927) Decouple netty server threads from message processing
[ https://issues.apache.org/jira/browse/GIRAPH-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Edunov updated GIRAPH-927: - Attachment: async.patch 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)
[jira] [Updated] (GIRAPH-927) Decouple netty server threads from message processing
[ https://issues.apache.org/jira/browse/GIRAPH-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Edunov updated GIRAPH-927: - Attachment: (was: GIRAPH-927.patch) 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)
[jira] [Updated] (GIRAPH-927) Decouple netty server threads from message processing
[ https://issues.apache.org/jira/browse/GIRAPH-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Edunov updated GIRAPH-927: - Attachment: GIRAPH-927.patch 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)
[jira] [Updated] (GIRAPH-927) Decouple netty server threads from message processing
[ https://issues.apache.org/jira/browse/GIRAPH-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Edunov updated GIRAPH-927: - Attachment: (was: GIRAPH-927.patch) 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)
[jira] [Updated] (GIRAPH-927) Decouple netty server threads from message processing
[ https://issues.apache.org/jira/browse/GIRAPH-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Edunov updated GIRAPH-927: - Attachment: GIRAPH-927.patch 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)
[jira] [Updated] (GIRAPH-927) Decouple netty server threads from message processing
[ https://issues.apache.org/jira/browse/GIRAPH-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Edunov updated GIRAPH-927: - Attachment: GIRAPH-927.patch 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)
