[ 
https://issues.apache.org/jira/browse/HIVE-24524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

László Bodor updated HIVE-24524:
--------------------------------
    Description: 
Tez already has a WIP patch for upgrading its shuffle handler to netty4. Netty4 
is told to be a possible performance improvement compared to Netty3. However, 
the refactor is not trivial, TEZ-4157 covers that more or less (the code bases 
are very similar).

Background:
netty4 migration guideline: https://netty.io/wiki/new-and-noteworthy-in-4.0.html
articles of possible performance improvement:
https://blog.twitter.com/engineering/en_us/a/2013/netty-4-at-twitter-reduced-gc-overhead.html
https://developer.squareup.com/blog/upgrading-a-reverse-proxy-from-netty-3-to-4/

  was:Tez already has a WIP patch for upgrading its shuffle handler to netty4. 
Netty4 is told to be a possible performance improvement compared to Netty3. 
However, the refactor is not trivial, TEZ-4157 covers that more or less (the 
code bases are very similar).


> LLAP ShuffleHandler: upgrade to netty4
> --------------------------------------
>
>                 Key: HIVE-24524
>                 URL: https://issues.apache.org/jira/browse/HIVE-24524
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: László Bodor
>            Assignee: László Bodor
>            Priority: Major
>
> Tez already has a WIP patch for upgrading its shuffle handler to netty4. 
> Netty4 is told to be a possible performance improvement compared to Netty3. 
> However, the refactor is not trivial, TEZ-4157 covers that more or less (the 
> code bases are very similar).
> Background:
> netty4 migration guideline: 
> https://netty.io/wiki/new-and-noteworthy-in-4.0.html
> articles of possible performance improvement:
> https://blog.twitter.com/engineering/en_us/a/2013/netty-4-at-twitter-reduced-gc-overhead.html
> https://developer.squareup.com/blog/upgrading-a-reverse-proxy-from-netty-3-to-4/



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to