[
https://issues.apache.org/jira/browse/THRIFT-2766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kai Li updated THRIFT-2766:
---------------------------
Description: Netty 4 provides fully asynchronous transport based on future
and memory pool management with a mixed algorithm of jemalloc and buddy
allocation. Both features improve the performance significantly. Although
Finagle by Twitter and Nifty by Facebook have already used Netty as the
underlying transport of their Thrift server and client, both are locked in to
Netty 3 due to their internal usage history. It is not very realistic to expect
them to upgrade all of their production codebase to use Netty 4 in the near
future. The only way to integrate the best of Thrift and the latest Netty is to
implement asynchronous transport in this project. (was: Netty 4 provides fully
asynchronous transport based on future and memory pool management with a mixed
algorithm of jemalloc and buddy allocation. Both features improve the
performance significantly. Although Finagle by Twitter and Nifty by Facebook
have already used Netty as the underlying transport of their Thrift server and
client, both are locked in to Netty 3 due to their internal usage history. It
is not very realistic to expect them to upgrade all of their production
codebase to use Netty 4 in the near future. The only way to integrate the best
of Thrift and Netty is to implement asynchronous transport in this project.)
> Implement asynchronous transport with Netty 4
> ---------------------------------------------
>
> Key: THRIFT-2766
> URL: https://issues.apache.org/jira/browse/THRIFT-2766
> Project: Thrift
> Issue Type: Improvement
> Components: Java - Library
> Reporter: Kai Li
> Labels: performance
>
> Netty 4 provides fully asynchronous transport based on future and memory pool
> management with a mixed algorithm of jemalloc and buddy allocation. Both
> features improve the performance significantly. Although Finagle by Twitter
> and Nifty by Facebook have already used Netty as the underlying transport of
> their Thrift server and client, both are locked in to Netty 3 due to their
> internal usage history. It is not very realistic to expect them to upgrade
> all of their production codebase to use Netty 4 in the near future. The only
> way to integrate the best of Thrift and the latest Netty is to implement
> asynchronous transport in this project.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
