Go to file
belliottsmith 2a2a21ec59 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-13 10:56:18 +02:00
all Initial STOMP protocol work from @sskachkov 2014-06-04 17:09:42 +09:00
buffer Introduce FastThreadLocal which uses an EnumMap and a predefined fixed set of possible thread locals 2014-06-13 10:56:18 +02:00
codec Introduce FastThreadLocal which uses an EnumMap and a predefined fixed set of possible thread locals 2014-06-13 10:56:18 +02:00
codec-dns DNS codec for Netty which is based on the work of [#1622]. 2014-06-10 09:57:06 +02:00
codec-http Introduce FastThreadLocal which uses an EnumMap and a predefined fixed set of possible thread locals 2014-06-13 10:56:18 +02:00
codec-memcache Introduce MessageAggregator and DecoderResultProvider 2014-06-05 16:51:14 +09:00
codec-socks Clean up the examples 2014-05-23 17:13:09 +09:00
codec-stomp Fix StompSubframeEncoderTest failure 2014-06-05 17:04:58 +09:00
common Introduce FastThreadLocal which uses an EnumMap and a predefined fixed set of possible thread locals 2014-06-13 10:56:18 +02:00
example Introduce MessageAggregator and DecoderResultProvider 2014-06-05 16:51:14 +09:00
handler Introduce FastThreadLocal which uses an EnumMap and a predefined fixed set of possible thread locals 2014-06-13 10:56:18 +02:00
license Preparation for porting OpenSSL support in 3.10 2014-05-17 20:01:30 +09:00
microbench Introduce FastThreadLocal which uses an EnumMap and a predefined fixed set of possible thread locals 2014-06-13 10:56:18 +02:00
tarball Update the version to 4.1.0.Alpha1-SNAPSHOT 2014-02-13 18:32:26 -08:00
testsuite Introduce MessageAggregator and DecoderResultProvider 2014-06-05 16:51:14 +09:00
transport Introduce FastThreadLocal which uses an EnumMap and a predefined fixed set of possible thread locals 2014-06-13 10:56:18 +02:00
transport-native-epoll Add an OpenSslEngine and the universal API for enabling SSL 2014-05-18 02:54:06 +09:00
transport-rxtx Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +09:00
transport-sctp Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +09:00
transport-udt Synchronized between 4.1 and master again (part 2) 2014-04-25 15:06:26 +09: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:36:54 +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:13:58 +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:30 +09:00
pom.xml DNS codec for Netty which is based on the work of [#1622]. 2014-06-10 09:57:06 +02:00
README.md Synchronized between 4.1 and master 2014-04-25 00:38:02 +09:00
run-example.sh Overall refactoring of the STOMP codec 2014-06-04 17:09:42 +09:00

Netty Project

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

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 versions takes place in each branch whose name is identical to <majorVersion>.<minorVersion>. For example, the development of 3.9 and 4.0 resides in the branch '3.9' and the branch '4.0' respectively.