[
https://issues.apache.org/jira/browse/GIRAPH-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13902043#comment-13902043
]
Pavan Kumar commented on GIRAPH-840:
------------------------------------
I just ran
mvn clean verify -Phadoop_0.20.203
and
mvn clean verify -Phadoop_0.23
both succeed
Avery can you please help understand the issue.
I did built the dependency tree for netty in rexter-io and see this
http://pastebin.com/q0FpwWwu
I find this wierd since it has "io.netty:netty:jar:3.6.3.Final:test" which is
incorrect.
Unable to reproduce locally since tests succeed.
> 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)
