Go to file
Norman Maurer e0ef01cf93 [#3888] Use 2 * cores as default minimum for pool arenas.
Motivation:

At the moment we use 1 * cores as default mimimum for pool arenas. This can easily lead to conditions as we use 2 * cores as default for EventLoop's when using NIO or EPOLL. If we choose a smaller number we will run into hotspots as allocation and deallocation needs to be synchronized on the PoolArena.

Modifications:

Change the default number of arenas to 2 * cores.

Result:

Less conditions when using the default settings.
2015-06-18 07:27:30 +02:00
all
buffer
codec
codec-dns
codec-haproxy
codec-http
codec-http2
codec-memcache
codec-mqtt
codec-socks
codec-stomp
codec-xml
common
example
handler
handler-proxy
license Let PoolThreadCache work even if allocation and deallocation Thread are different 2015-05-27 14:38:11 +02:00
microbench
resolver
resolver-dns
tarball
testsuite
testsuite-osgi
transport
transport-native-epoll
transport-rxtx
transport-sctp
transport-udt
.fbprefs
.gitignore
.travis.yml
CONTRIBUTING.md
LICENSE.txt
NOTICE.txt
pom.xml
README.md
run-example.sh

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.