Go to file
Norman Maurer d6c23d0af9 Remove HashMap for lookup name / ctx from DefaultChannelPipeline to reduce memory footprint
Motivation:

If you start to have 1M+ concurrent connections memory footprint can be come a big issue. We should try to reduce it as much as possible in the core of netty.

Modifications:

- Remove HashMap that was used to store name to ctx mapping. This was only used for validation and access a handler by name. As a pipeline is not expected to be very long (like 100+ handlers) we can just walk the linked list structure to find the ctx with a given name.

Result:

Less memory footprint of the DefaultChannelPipeline.
2015-11-20 06:10:39 -08:00
all [maven-release-plugin] prepare release netty-4.0.33.Final 2015-11-03 14:18:17 +01:00
buffer Fix setBytes on read-only ByteBuffer 2015-11-17 22:45:16 -08:00
codec [maven-release-plugin] prepare release netty-4.0.33.Final 2015-11-03 14:18:17 +01:00
codec-haproxy [maven-release-plugin] prepare release netty-4.0.33.Final 2015-11-03 14:18:17 +01:00
codec-http Make HttpHeaders.set(self) a no-op consistently rather than having some implementations throw and others not 2015-11-06 07:12:50 -08:00
codec-socks [maven-release-plugin] prepare release netty-4.0.33.Final 2015-11-03 14:18:17 +01:00
common configurable service thread name prefix 2015-11-05 08:51:59 +01:00
example [maven-release-plugin] prepare release netty-4.0.33.Final 2015-11-03 14:18:17 +01:00
handler ApplicationProtocolNegotiationHandler failure behavior 2015-11-07 09:34:08 -08:00
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
microbench [maven-release-plugin] prepare release netty-4.0.33.Final 2015-11-03 14:18:17 +01:00
tarball [maven-release-plugin] prepare release netty-4.0.33.Final 2015-11-03 14:18:17 +01:00
testsuite [maven-release-plugin] prepare release netty-4.0.33.Final 2015-11-03 14:18:17 +01:00
testsuite-osgi [maven-release-plugin] prepare release netty-4.0.33.Final 2015-11-03 14:18:17 +01:00
transport Remove HashMap for lookup name / ctx from DefaultChannelPipeline to reduce memory footprint 2015-11-20 06:10:39 -08:00
transport-native-epoll Store reference to IovArray in the EpollEventLoop to reduce thread local access. 2015-11-20 06:07:44 -08:00
transport-rxtx [maven-release-plugin] prepare release netty-4.0.33.Final 2015-11-03 14:18:17 +01:00
transport-sctp [maven-release-plugin] prepare release netty-4.0.33.Final 2015-11-03 14:18:17 +01:00
transport-udt [maven-release-plugin] prepare release netty-4.0.33.Final 2015-11-03 14:18:17 +01: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 Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:35:22 +02:00
pom.xml Update ALPN boot version 2015-11-07 09:38:20 -08:00
README.md Fix the 'branches to look' section 2015-10-27 13:58:06 +01:00
run-example.sh Add logLevel property to enable different log levels for the examples. 2014-11-21 10:48:13 +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.