andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
5,808 Commits 27 Branches 234 Tags 84 MiB
Java 99.8%
Shell 0.1%
1ac2ff8d7b
Go to file
belliottsmith 1ac2ff8d7b Introduce FastThreadLocal which uses an EnumMap and a predefined fixed set of possible thread locals 
Motivation:
Provide a faster ThreadLocal implementation

Modification:
Add a "FastThreadLocal" which uses an EnumMap and a predefined fixed set of possible thread locals (all of the static instances created by netty) that is around 10-20% faster than standard ThreadLocal in my benchmarks (and can be seen having an effect in the direct PooledByteBufAllocator benchmark that uses the DEFAULT ByteBufAllocator which uses this FastThreadLocal, as opposed to normal instantiations that do not, and in the new RecyclableArrayList benchmark);

Result:
Improved performance
2014-06-12 15:43:20 +02:00
all Use a forked exec-maven-plugin instead of maven-antrun-plugin 2014-05-23 20:06:12 +09:00
buffer Introduce FastThreadLocal which uses an EnumMap and a predefined fixed set of possible thread locals 2014-06-12 15:43:20 +02:00
codec [#2525] Use VoidChannelPromise in MessageToMessageEncoder when possible 2014-06-01 19:26:09 +02:00
codec-http [#2542] HTTP post request decoder does not support quoted boundaries 2014-06-08 21:57:43 +02:00
codec-socks Clean up the examples 2014-05-23 17:19:34 +09:00
common Introduce FastThreadLocal which uses an EnumMap and a predefined fixed set of possible thread locals 2014-06-12 15:43:20 +02:00
example OkResponseHandler should return a FullHttpResponse. 2014-06-03 09:44:04 +02:00
handler [#2494] Fix data curruption by ChannelTrafficShapingHandler 2014-06-03 08:38:23 +02:00
license Preparation for porting OpenSSL support in 3.10 2014-05-17 20:01:47 +09:00
microbench Introduce FastThreadLocal which uses an EnumMap and a predefined fixed set of possible thread locals 2014-06-12 15:43:20 +02:00
tarball [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
testsuite Add an OpenSslEngine and the universal API for enabling SSL 2014-05-18 02:54:23 +09:00
transport Introduce FastThreadLocal which uses an EnumMap and a predefined fixed set of possible thread locals 2014-06-12 15:43:20 +02:00
transport-native-epoll Add an OpenSslEngine and the universal API for enabling SSL 2014-05-18 02:54:23 +09:00
transport-rxtx [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
transport-sctp [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
transport-udt [maven-release-plugin] prepare for next development iteration 2014-04-30 15:40:54 +02:00
.fbfilter.xml Update license headers 2012-06-04 13:31:44 -07:00
.fbprefs Updated Find Bugs configuration 2009-03-04 10:33:09 +00:00
.gitignore Add JVM crash logs to .gitignore 2014-05-18 21:37:12 +09:00
.travis.yml Travis CI branch whitelisting 2013-03-11 09:55:43 +09:00
CONTRIBUTING.md Move the pull request guide to the developer guide 2014-03-12 13:18:14 +09:00
LICENSE.txt Relicensed to Apache License v2 2009-08-28 07:15:49 +00:00
NOTICE.txt Preparation for porting OpenSSL support in 3.10 2014-05-17 20:01:47 +09:00
pom.xml Require Maven 3.1.1 or above 2014-06-04 03:15:38 +09:00
README.md Update README.md 2014-01-16 14:38:36 +09:00
run-example.sh Use a forked exec-maven-plugin instead of maven-antrun-plugin 2014-05-23 20:06:12 +09:00

README.md

Netty Project

Netty is an asynchronous event-driven network application framework for rapid development of maintainable high performance protocol servers & clients.

Links

How to build

For the detailed information about building and developing Netty, please visit the developer guide. This page only gives very basic information.

You require the following to build Netty:

Note that this is build-time requirement. JDK 5 (for 3.x) or 6 (for 4.0+) is enough to run your Netty-based application.

Branches to look

The 'master' branch is where the development of the latest major version lives on. The development of all other major versions takes place in each branch whose name is identical to its major version number. For example, the development of 3.x and 4.x resides in the branch '3' and the branch '4' respectively.