Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@giraph.apache.org
Date: Tue, 18 Feb 2014 03:12:21 +0000 (UTC)
From: "Pavan Kumar (JIRA)" <jira@apache.org>
To: giraph-dev@incubator.apache.org
Message-ID: <JIRA.12692728.1391364330571.55643.1392693141956@arcas>
In-Reply-To: <JIRA.12692728.1391364330571@arcas>
References: <JIRA.12692728.1391364330571@arcas>
Subject: [jira] [Commented] (GIRAPH-840) Upgrade to netty 4
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Pavan Kumar commented on GIRAPH-840:
------------------------------------

Result of the build
http://pastebin.com/T0eUMdxR


> Upgrade to netty 4
> ------------------
>
>                 Key: GIRAPH-840
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-840
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Pavan Kumar
>            Assignee: Pavan Kumar
>             Fix For: 1.1.0
>
>         Attachments: GIRAPH-840.patch, GIRAPH-840.patch
>
>
> Off late netty 4 has earned so much praise in the community. For example, 
> https://blog.twitter.com/2013/netty-4-at-twitter-reduced-gc-overhead
> A switch to netty 4 enables a significant reduction in gc pressure and also huge performance gains. I started working on this last Sunday and have a patch that shows performance gains on the order of 15-25% (total execution time) for some applications at Facebook. However, I only tested it with hadoop_facebook. So there might be issues with SASL path. 
> I will release the patch today and want to open up a discussion if anyone is using the secure feature anymore. If not we can just deprecate it.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)